Bug 14279 - qemux86 failed to shutdown
Summary: qemux86 failed to shutdown
Status: RESOLVED DUPLICATE of bug 14128
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 3.3 M4
Assignee: Unassigned
QA Contact:
URL:
Whiteboard: AB-INT
Depends on:
Blocks:
 
Reported: 2021-03-04 23:06 UTC by Aníbal Limón
Modified: 2021-03-11 19:40 UTC (History)
4 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 Aníbal Limón 2021-03-04 23:06:11 UTC 
Log,

...
2021-03-04 04:10:21,781 - oe-selftest - INFO - 0: 3/3 3/4 (0.10s) (meta_ide.MetaIDE.test_meta_ide_had_installed_meta_ide_support)
2021-03-04 04:14:43,498 - oe-selftest - INFO - runqemu.QemuTest.test_qemu_can_shutdown (subunit.RemotedTestCase)
2021-03-04 04:14:43,498 - oe-selftest - INFO -  ... FAIL
2021-03-04 04:14:43,499 - oe-selftest - INFO - 1: 1/1 4/4 (391.46s) (runqemu.QemuTest.test_qemu_can_shutdown)
2021-03-04 04:14:43,499 - oe-selftest - INFO - testtools.testresult.real._StringException: Traceback (most recent call last):
  File "/home/pokybuild/yocto-worker/qemux86/build/meta/lib/oeqa/selftest/cases/runqemu.py", line 191, in test_qemu_can_shutdown
    self.assertTrue(qemu_shutdown_succeeded, 'Failed: %s does not shutdown within timeout(%s)' % (self.machine, shutdown_timeout))
  File "/usr/lib/python3.6/unittest/case.py", line 682, in assertTrue
    raise self.failureException(msg)
AssertionError: False is not true : Failed: qemux86 does not shutdown within timeout(120)
...

From,

https://autobuilder.yoctoproject.org/typhoon/#/builders/59/builds/3151/steps/19/logs/stdio
Comment 1 Alexandre Belloni 2021-03-11 19:40:57 UTC 
Merge of all the qemu does not shutdown within timeout issues

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