STATUS: IDLE BUILD: 2.4 M2: rc2-8e15e9b6e478f6368034519b2a8fd3c7ea71d23b ENVIRONMENT: CentOS 7.1 x86_64 STEPS TO REPRODUCE: 1. Clone poky 2. source environment 3. cd build 4. oe-sleftest -r runtime_test.TestImage.test_testimage_dnf EXPECTED OUTCOME: runtime_test.TestImage.test_testimage_dnf: pass ACTUAL OUTCOME: TestImage.test_testimage_dnf - Testcase 1883: FAILED ===================================================================== 2017-07-26 18:34:47,350 - oe-selftest - INFO - FAIL [300.054s]: test_testimage_dnf (runtime_test.TestImage) 2017-07-26 18:34:47,350 - oe-selftest - INFO - ---------------------------------------------------------------------- 2017-07-26 18:34:47,350 - oe-selftest - INFO - Traceback (most recent call last): File "/home/ab/autobuilder/yocto-worker/nightly-oe-selftest-centos7/build/meta/lib/oeqa/core/decorator/__init__.py", line 32, in wrapped_f return func(*args, **kwargs) File "/home/ab/autobuilder/yocto-worker/nightly-oe-selftest-centos7/build/meta/lib/oeqa/selftest/cases/runtime_test.py", line 151, in test_testimage_dnf bitbake('-c testimage core-image-full-cmdline') File "/home/ab/autobuilder/yocto-worker/nightly-oe-selftest-centos7/build/meta/lib/oeqa/utils/commands.py", line 213, in bitbake return runCmd(cmd, ignore_status, timeout, output_log=output_log, **options) File "/home/ab/autobuilder/yocto-worker/nightly-oe-selftest-centos7/build/meta/lib/oeqa/utils/commands.py", line 191, in runCmd raise AssertionError("Command '%s' returned non-zero exit status %d:\n%s" % (command, result.status, exc_output)) AssertionError: Command 'bitbake -c testimage core-image-full-cmdline' returned non-zero exit status 1:
Need the full logs for the failure, this much doesn't show the actual failure.
(In reply to comment #1) > Need the full logs for the failure, this much doesn't show the actual > failure. I put the complete records in attachment
Created attachment 3907 [details] full_log
Attached logs don't match the failure in the bug report. Did you mix up the logs?
(In reply to comment #4) > Attached logs don't match the failure in the bug report. Did you mix up the > logs? Certainly I was wrong to register, an apology, I attached the registration of TestImage.test_testimage_dnf
Created attachment 3911 [details] dnf_failed
Status change
This is another autobuilder setup issue. To quote from the logs: | runqemu - ERROR - Error: There are no available tap devices to use for networking, | runqemu - ERROR - and I see /etc/runqemu-nosudo exists, so I am not going to try creating | runqemu - ERROR - a new one with sudo.