Created attachment 4039 [details] 2.4.rc1.log tests were executed and The pass rate goes back the percentage, observing 10 failures on the results. poky : 592c3449697ce39bf07864fafd7f0a61ca230561 2.4 rc1 HW: NUC 6i5SYH image: https://autobuilder.yocto.io/pub/releases/yocto-2.4.rc1/machines/genericx86-64/core-image-sato-sdk-ptest-genericx86-64.hddimg https://wiki.yoctoproject.org/wiki/Ptest_592c3449697ce39bf07864fafd7f0a61ca230561 STEPS: automatic 1. Download pTest image from autobuilder( you can find core-image-sato-sdk image in pTest directory) * we test it on NUC with genericx86-64 2. Install the image on DUT (using legacy boot) 3) Configure the network so it be able to work externally: - Export the proxy using "export http_proxy=<add your proxy link>" command eg And check if you have internet connection, typing on terminal: $ wget www.google.com 4. In command line type $ ptest-runner > ptest.log EXPECTED OUTCOME: The pass rate goes up the percentage ACTUAL OUTCOME: The pass rate goes back the percentage =============================================================== FAIL: unzip (bad archive) FAIL: sed nonexistent label FAIL: sed NUL in command =================================================================NOTES: full log in attachment
Testing in QEMU, I got these results: PASS: 504 FAIL: 14 First of all, many of the tests do not test Busybox at all, as due to UPDATE_ALTERNATIVES many utilities come from alternative (usually more complete implementation) packages. For example: unzip -> /usr/bin/unzip.unzip ls->/bin/ls.coreutils hostname->/bin/busybox.nosuid cpio->/bin/cpio.cpio These are the tests that fail FAIL: cpio lists hardlinks FAIL: hostname-d-works FAIL: ls-l-works FAIL: ls-s-works FAIL: sed embedded NUL FAIL: sed NUL in command FAIL: sed append autoinserts newline FAIL: sed nonexistent label FAIL: unzip (subdir only) FAIL: unzip (bad archive) *FAIL: wget--O-overrides--P *FAIL: wget-handles-empty-path *FAIL: wget-retrieves-google-index *FAIL: wget-supports--P Reasons for failures of some of them: FAIL: hostname-d-works ++ busybox hostname -f hostname: genericx86-64: Unknown host Remedy: place hostname (from /etc/hostname) to /etc/hosts Something like: 127.0.1.1 genericx86-64 FAIL: ls-l-works FAIL: ls-s-works These two tests fail due to the fact that ls is not the Busybox implementation: In our case ls->/bin/ls.coreutils So this is a valid (but harmless failure), the test checks if ls behaves exactly as expected by Busybox. Should be probably removed, as they are pointless. FAIL: unzip (subdir only): The test requires "zip", which is not installed in the image. It is possible to fix this in busybox-ptest recipe addid "zip" via RDEPEND-ptest. FAIL: unzip (bad archive) The test fails because "uuencode" is not installed n the image. The default .config for Busybox is: "CONFIG_UUENCODE is not set" so in principle this is fixable. (Alternatively, if CONFIG_UUENCODE is not set, disable/remove the test) FAIL: sed embedded NUL FAIL: sed NUL in command FAIL: sed append autoinserts newline FAIL: sed nonexistent label These tests test sed->sed.sed, not the Busybox implementation of "sed". However, when switching to the Busybox version, errors still persisted. Needs more analysis. **** FAIL: wget--O-overrides--P FAIL: wget-handles-empty-path FAIL: wget-retrieves-google-index FAIL: wget-supports--P QEMU specific, failures not observed with proper network.
tests were executed and The pass rate goes up the percentage, observing 9 failures on the results. POKY : 2.4_M4_r2 COMMIT:da05a01423a60a23cd1073eb0ad3776e5bf4f2a8 HW: NUC 6i5SYH IMAGES: https://autobuilder.yocto.io/pub/releases/yocto-2.4.rc2/machines/genericx86-64/core-image-sato-sdk-ptest-genericx86-64.hddimg Results Chart table: https://wiki.yoctoproject.org/wiki/Ptest_da05a01423a60a23cd1073eb0ad3776e5bf4f2a8 note: full=log in attachent
Created attachment 4071 [details] full_log
Closing this as RESOLVED/FIXED, but individual test that fail need to be filed as separate bugs.