Bug 13370 - oe-selftest runqemu test case failed for qemuppc: timeout error
Summary: oe-selftest runqemu test case failed for qemuppc: timeout error
Status: RESOLVED DUPLICATE of bug 13309
Alias: None
Product: Functional (self) Testing
Classification: QA/Testing
Component: oe-selftest (show other bugs)
Version: 2.8
Hardware: x86 Multiple
: Undecided normal
Target Milestone: ---
Assignee: Apoorv
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2019-05-30 01:38 UTC by Chen Qi
Modified: 2019-05-30 13:30 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chen Qi 2019-05-30 01:38:17 UTC 
The link is:
https://autobuilder.yoctoproject.org/typhoon/#/builders/63/builds/636/steps/7/logs/step3d

2019-05-29 10:01:26,752 - oe-selftest - INFO - ======================================================================
2019-05-29 10:01:26,752 - oe-selftest - INFO - FAIL: runqemu.QemuTest.test_qemu_can_shutdown (subunit.RemotedTestCase)
2019-05-29 10:01:26,753 - oe-selftest - INFO - ----------------------------------------------------------------------
2019-05-29 10:01:26,753 - oe-selftest - INFO - testtools.testresult.real._StringException: Traceback (most recent call last):
  File "/home/pokybuild/yocto-worker/qemuppc/build/meta/lib/oeqa/selftest/cases/runqemu.py", line 189, in test_qemu_can_shutdown
    self.assertTrue(qemu_shutdown_succeeded, 'Failed: %s does not shutdown within timeout(%s)' % (self.machine, shutdown_timeout))
  File "/usr/lib64/python3.6/unittest/case.py", line 699, in assertTrue
    raise self.failureException(msg)
AssertionError: False is not true : Failed: qemuppc does not shutdown within timeout(120)
[snip]
2019-05-29 10:01:32,738 - oe-selftest - INFO - RESULTS - runqemu.QemuTest.test_qemu_can_shutdown: FAILED (199.88s)
Comment 1 Richard Purdie 2019-05-30 13:30:38 UTC 
Duplicate of 13309

*** This bug has been marked as a duplicate of bug 13309 ***