auto.conf settings:
MACHINE = "qemux86"
DISTRO = "poky"
SDKMACHINE = "i686"
PACKAGE_CLASSES = "package_rpm package_deb package_ipk"
DL_DIR = '/srv/autobuilder/autobuilder.yocto.io/current_sources'
SSTATE_DIR ?= '/srv/autobuilder/autobuilder.yocto.io/pub/sstate'
INHERIT += 'image-buildinfo'
IMAGE_BUILDINFO_VARS:append = ' IMAGE_BASENAME IMAGE_NAME'
IMAGE_INSTALL:append = ' ssh-pregen-hostkeys'
QEMU_USE_KVM = 'True'
INHERIT += 'report-error'
PREMIRRORS = ''
BB_GENERATE_MIRROR_TARBALLS = '1'
BB_NUMBER_THREADS = '16'
BB_NUMBER_PARSE_THREADS = '16'
PARALLEL_MAKE = '-j 16 -l 52'
BB_PRESSURE_MAX_CPU = '10000'
BB_PRESSURE_MAX_IO = '10000'
XZ_MEMLIMIT = '5%'
XZ_THREADS = '8'
ZSTD_THREADS = '8'
BB_TASK_NICE_LEVEL = '5'
BB_TASK_NICE_LEVEL:task-testimage = '0'
BB_TASK_IONICE_LEVEL = '2.7'
BB_TASK_IONICE_LEVEL:task-testimage = '2.1'
INHERIT += 'testimage'
TEST_QEMUBOOT_TIMEOUT = '1500'
SANITY_TESTED_DISTROS = ''
SDK_EXT_TYPE = 'minimal'
SDK_INCLUDE_TOOLCHAIN = '1'
ESDK_LOCAL_CONF_REMOVE:append = 'BB_HASHSERVE'
BB_DISKMON_DIRS = 'STOPTASKS,${TMPDIR},1G,100K STOPTASKS,${DL_DIR},1G STOPTASKS,${SSTATE_DIR},1G STOPTASKS,/tmp,100M,30K HALT,${TMPDIR},100M,1K HALT,${DL_DIR},100M HALT,${SSTATE_DIR},100M HALT,/tmp,10M,1K'
BB_HASHSERVE = 'hashserv.yocto.io:8686'
RUNQEMU_TMPFS_DIR = '/home/pokybuild/tmp'
BB_HEARTBEAT_EVENT = '60'
BB_LOG_HOST_STAT_ON_INTERVAL = '1'
BB_LOG_HOST_STAT_CMDS_INTERVAL = 'oe-time-dd-test.sh -c 100 -t 15'
BB_LOG_HOST_STAT_ON_FAILURE = '1'
BB_LOG_HOST_STAT_CMDS_FAILURE = 'oe-time-dd-test.sh -l'
Running '. ./oe-init-build-env; ${SCRIPTSDIR}/checkvnc; DISPLAY=:1 oe-selftest -a -t machine -t toolchain-system -j 15' with output to /home/pokybuild/yocto-worker/qemux86/build/build/command-3-cmds.log
### Shell environment set up for builds. ###
You can now run 'bitbake <target>'
Common targets are:
core-image-minimal
core-image-full-cmdline
core-image-sato
core-image-weston
meta-toolchain
meta-ide-support
You can also run generated qemu images with a command like 'runqemu qemux86'
Other commonly useful commands are:
- 'devtool' and 'recipetool' handle common recipe tasks
- 'bitbake-layers' handles common layer tasks
- 'oe-pkgdata-util' handles common target package tasks
2023-09-12 17:02:12,989 - oe-selftest - INFO - Adding layer libraries:
2023-09-12 17:02:12,989 - oe-selftest - INFO - /home/pokybuild/yocto-worker/qemux86/build/meta/lib
2023-09-12 17:02:12,990 - oe-selftest - INFO - /home/pokybuild/yocto-worker/qemux86/build/meta-yocto-bsp/lib
2023-09-12 17:02:12,990 - oe-selftest - INFO - /home/pokybuild/yocto-worker/qemux86/build/meta-selftest/lib
2023-09-12 17:02:12,991 - oe-selftest - INFO - Running bitbake -e to test the configuration is valid/parsable
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint: git branch -m <name>
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint: git branch -m <name>
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint: git branch -m <name>
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint: git branch -m <name>
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint: git branch -m <name>
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint: git branch -m <name>
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint: git branch -m <name>
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint: git branch -m <name>
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint: git branch -m <name>
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint: git branch -m <name>
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint: git branch -m <name>
2023-09-12 17:03:04,475 - oe-selftest - INFO - gcc.GccLibSspSelfTestSystemEmulated.test_libssp (subunit.RemotedTestCase)
2023-09-12 17:03:04,477 - oe-selftest - INFO - ... skipped 'Target does not use libssp\n'
2023-09-12 17:03:04,477 - oe-selftest - INFO - 5: 1/1 1/15 (47.41s) (0 failed) (gcc.GccLibSspSelfTestSystemEmulated.test_libssp)
2023-09-12 17:03:04,477 - oe-selftest - INFO - Target does not use libssp
2023-09-12 17:04:00,103 - oe-selftest - INFO - binutils.BinutilsCrossSelfTest.test_binutils (subunit.RemotedTestCase)
2023-09-12 17:04:00,104 - oe-selftest - INFO - ... ok
2023-09-12 17:04:00,104 - oe-selftest - INFO - 0: 1/3 2/15 (103.05s) (0 failed) (binutils.BinutilsCrossSelfTest.test_binutils)
2023-09-12 17:04:44,347 - oe-selftest - INFO - meta_ide.MetaIDE.test_meta_ide_can_build_cpio_project (subunit.RemotedTestCase)
2023-09-12 17:04:44,347 - oe-selftest - INFO - ... ok
2023-09-12 17:04:44,347 - oe-selftest - INFO - 9: 1/3 3/15 (46.24s) (0 failed) (meta_ide.MetaIDE.test_meta_ide_can_build_cpio_project)
2023-09-12 17:04:45,159 - oe-selftest - INFO - meta_ide.MetaIDE.test_meta_ide_can_compile_c_program (subunit.RemotedTestCase)
2023-09-12 17:04:45,159 - oe-selftest - INFO - ... ok
2023-09-12 17:04:45,159 - oe-selftest - INFO - 9: 2/3 4/15 (0.81s) (0 failed) (meta_ide.MetaIDE.test_meta_ide_can_compile_c_program)
2023-09-12 17:04:45,166 - oe-selftest - INFO - meta_ide.MetaIDE.test_meta_ide_had_installed_meta_ide_support (subunit.RemotedTestCase)
2023-09-12 17:04:45,166 - oe-selftest - INFO - ... ok
2023-09-12 17:04:45,166 - oe-selftest - INFO - 9: 3/3 5/15 (0.01s) (0 failed) (meta_ide.MetaIDE.test_meta_ide_had_installed_meta_ide_support)
2023-09-12 17:05:52,276 - oe-selftest - INFO - binutils.BinutilsCrossSelfTest.test_gas (subunit.RemotedTestCase)
2023-09-12 17:05:52,278 - oe-selftest - INFO - ... ok
2023-09-12 17:05:52,278 - oe-selftest - INFO - 0: 2/3 6/15 (112.17s) (0 failed) (binutils.BinutilsCrossSelfTest.test_gas)
2023-09-12 17:06:56,006 - oe-selftest - INFO - binutils.BinutilsCrossSelfTest.test_ld (subunit.RemotedTestCase)
2023-09-12 17:06:56,009 - oe-selftest - INFO - ... ok
2023-09-12 17:06:56,009 - oe-selftest - INFO - 0: 3/3 7/15 (63.73s) (0 failed) (binutils.BinutilsCrossSelfTest.test_ld)
2023-09-12 17:07:39,146 - oe-selftest - INFO - gcc.GccLibAtomicSelfTestSystemEmulated.test_libatomic (subunit.RemotedTestCase)
2023-09-12 17:07:39,146 - oe-selftest - INFO - ... ok
2023-09-12 17:07:39,147 - oe-selftest - INFO - 2: 1/1 8/15 (322.08s) (0 failed) (gcc.GccLibAtomicSelfTestSystemEmulated.test_libatomic)
2023-09-12 17:07:42,356 - oe-selftest - INFO - runqemu.QemuTest.test_qemu_can_shutdown (subunit.RemotedTestCase)
2023-09-12 17:07:42,357 - oe-selftest - INFO - ... FAIL
Stderr:
2023-09-12 17:02:17,059 - oe-selftest - INFO - Adding: "include selftest.inc" in /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/conf/local.conf
2023-09-12 17:02:17,059 - oe-selftest - INFO - Adding: "include bblayers.inc" in bblayers.conf
Loading cache...done.
rootfs file:
Qemu log file: /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/testimage/qemu_boot_log.20230912170429
SSH log file: /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/testimage/ssh_target_log.20230912170429
QMP Available for connection at /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/.st4uom63
Created listening socket for qemu serial console on: 127.0.0.1:49695
Created listening socket for qemu serial console on: 127.0.0.1:54179
launchcmd=runqemu nographic /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/deploy/images/qemux86/core-image-minimal-qemux86.qemuboot.conf tcpserial=49695:54179 bootparams=" printk.time=1" qemuparams="-pidfile /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/pidfile_1772097 -S -qmp unix:./.kor3bh36,server,wait -qmp unix:./.st4uom63,server,nowait"
runqemu started, pid is 2000267
waiting at most 300 seconds for qemu pid (09/12/23 17:04:31)
QMP Initializing to /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/.kor3bh36
QMP Connecting to /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/.kor3bh36
QMP connected to QEMU at 09/12/23 17:04:31 and took 0.5379478931427002 seconds
QMP released QEMU at 09/12/23 17:04:32 and took 0.07902669906616211 seconds from connect
qemu started in 0.6148955821990967 seconds - qemu procces pid is 2000318 (09/12/23 17:04:32)
Target IP: None
Server IP: None
Starting logging thread
Starting thread event loop
Connection request received
Setting connection established event
Output from runqemu:
runqemu - INFO - Using /home/pokybuild/bin/runqemu-renice to renice
runqemu - INFO - Continuing with the following parameters:
KERNEL: [/home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/deploy/images/qemux86/bzImage]
MACHINE: [qemux86]
FSTYPE: [ext4]
ROOTFS: [/home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/deploy/images/qemux86/core-image-minimal-qemux86-20230912170303.rootfs.ext4]
CONFFILE: [/home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/deploy/images/qemux86/core-image-minimal-qemux86.qemuboot.conf]
runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap0.lock failed: [Errno 11] Resource temporarily unavailable
runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap1.lock failed: [Errno 11] Resource temporarily unavailable
runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap2.lock failed: [Errno 11] Resource temporarily unavailable
runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap3.lock failed: [Errno 11] Resource temporarily unavailable
runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap4.lock failed: [Errno 11] Resource temporarily unavailable
runqemu - INFO - Using preconfigured tap device tap5
runqemu - INFO - If this is not intended, touch /tmp/qemu-tap-locks/tap5.skip to make runqemu skip tap5.
runqemu - INFO - Network configuration: ip=192.168.7.12::192.168.7.11:255.255.255.0::eth0:off:8.8.8.8
runqemu - INFO - Running /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/work/x86_64-linux/qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin/qemu-system-i386 -device virtio-net-pci,netdev=net0,mac=52:54:00:12:34:0c -netdev tap,id=net0,ifname=tap5,script=no,downscript=no -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0 -drive file=/home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/deploy/images/qemux86/core-image-minimal-qemux86-20230912170303.rootfs.ext4,if=virtio,format=raw -usb -device usb-tablet -cpu IvyBridge -machine q35 -smp 4 -m 256 -serial tcp:127.0.0.1:49695 -serial tcp:127.0.0.1:54179 -pidfile /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/pidfile_1772097 -S -qmp unix:./.kor3bh36,server,wait -qmp unix:./.st4uom63,server,nowait -serial mon:stdio -nographic -kernel /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/deploy/images/qemux86/bzImage -append 'root=/dev/vda rw ip=192.168.7.12::192.168.7.11:255.255.255.0::eth0:off:8.8.8.8 console=ttyS0 console=ttyS1 oprofile.timer=1 tsc=reliable no_timer_check rcupdate.rcu_expedited=1 printk.time=1'
runqemu - INFO - Host uptime: 88954.56
Waiting at most 1000 seconds for login banner (09/12/23 17:04:32)
Connection from 127.0.0.1:59384
Reached login banner in 60.64575529098511 seconds (09/12/23 17:05:32, 1694538332.6520703)
Logged as root in serial console
2023-09-12 17:07:42,357 - oe-selftest - INFO - 10: 1/1 9/15 (193.00s) (0 failed) (runqemu.QemuTest.test_qemu_can_shutdown)
2023-09-12 17:07:42,358 - 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 192, 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.11/unittest/case.py", line 715, in assertTrue
raise self.failureException(msg)
AssertionError: False is not true : Failed: qemux86 does not shutdown within timeout(120)
Stderr:
2023-09-12 17:02:17,059 - oe-selftest - INFO - Adding: "include selftest.inc" in /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/conf/local.conf
2023-09-12 17:02:17,059 - oe-selftest - INFO - Adding: "include bblayers.inc" in bblayers.conf
Loading cache...done.
rootfs file:
Qemu log file: /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/testimage/qemu_boot_log.20230912170429
SSH log file: /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/testimage/ssh_target_log.20230912170429
QMP Available for connection at /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/.st4uom63
Created listening socket for qemu serial console on: 127.0.0.1:49695
Created listening socket for qemu serial console on: 127.0.0.1:54179
launchcmd=runqemu nographic /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/deploy/images/qemux86/core-image-minimal-qemux86.qemuboot.conf tcpserial=49695:54179 bootparams=" printk.time=1" qemuparams="-pidfile /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/pidfile_1772097 -S -qmp unix:./.kor3bh36,server,wait -qmp unix:./.st4uom63,server,nowait"
runqemu started, pid is 2000267
waiting at most 300 seconds for qemu pid (09/12/23 17:04:31)
QMP Initializing to /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/.kor3bh36
QMP Connecting to /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/.kor3bh36
QMP connected to QEMU at 09/12/23 17:04:31 and took 0.5379478931427002 seconds
QMP released QEMU at 09/12/23 17:04:32 and took 0.07902669906616211 seconds from connect
qemu started in 0.6148955821990967 seconds - qemu procces pid is 2000318 (09/12/23 17:04:32)
Target IP: None
Server IP: None
Starting logging thread
Starting thread event loop
Connection request received
Setting connection established event
Output from runqemu:
runqemu - INFO - Using /home/pokybuild/bin/runqemu-renice to renice
runqemu - INFO - Continuing with the following parameters:
KERNEL: [/home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/deploy/images/qemux86/bzImage]
MACHINE: [qemux86]
FSTYPE: [ext4]
ROOTFS: [/home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/deploy/images/qemux86/core-image-minimal-qemux86-20230912170303.rootfs.ext4]
CONFFILE: [/home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/deploy/images/qemux86/core-image-minimal-qemux86.qemuboot.conf]
runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap0.lock failed: [Errno 11] Resource temporarily unavailable
runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap1.lock failed: [Errno 11] Resource temporarily unavailable
runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap2.lock failed: [Errno 11] Resource temporarily unavailable
runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap3.lock failed: [Errno 11] Resource temporarily unavailable
runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap4.lock failed: [Errno 11] Resource temporarily unavailable
runqemu - INFO - Using preconfigured tap device tap5
runqemu - INFO - If this is not intended, touch /tmp/qemu-tap-locks/tap5.skip to make runqemu skip tap5.
runqemu - INFO - Network configuration: ip=192.168.7.12::192.168.7.11:255.255.255.0::eth0:off:8.8.8.8
runqemu - INFO - Running /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/work/x86_64-linux/qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin/qemu-system-i386 -device virtio-net-pci,netdev=net0,mac=52:54:00:12:34:0c -netdev tap,id=net0,ifname=tap5,script=no,downscript=no -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0 -drive file=/home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/deploy/images/qemux86/core-image-minimal-qemux86-20230912170303.rootfs.ext4,if=virtio,format=raw -usb -device usb-tablet -cpu IvyBridge -machine q35 -smp 4 -m 256 -serial tcp:127.0.0.1:49695 -serial tcp:127.0.0.1:54179 -pidfile /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/pidfile_1772097 -S -qmp unix:./.kor3bh36,server,wait -qmp unix:./.st4uom63,server,nowait -serial mon:stdio -nographic -kernel /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/deploy/images/qemux86/bzImage -append 'root=/dev/vda rw ip=192.168.7.12::192.168.7.11:255.255.255.0::eth0:off:8.8.8.8 console=ttyS0 console=ttyS1 oprofile.timer=1 tsc=reliable no_timer_check rcupdate.rcu_expedited=1 printk.time=1'
runqemu - INFO - Host uptime: 88954.56
Waiting at most 1000 seconds for login banner (09/12/23 17:04:32)
Connection from 127.0.0.1:59384
Reached login banner in 60.64575529098511 seconds (09/12/23 17:05:32, 1694538332.6520703)
Logged as root in serial console
2023-09-12 17:09:38,150 - oe-selftest - INFO - gcc.GccLibItmSelfTestSystemEmulated.test_libitm (subunit.RemotedTestCase)
2023-09-12 17:09:38,151 - oe-selftest - INFO - ... ok
2023-09-12 17:09:38,151 - oe-selftest - INFO - 4: 1/1 10/15 (441.09s) (0 failed) (gcc.GccLibItmSelfTestSystemEmulated.test_libitm)
2023-09-12 17:15:10,329 - oe-selftest - INFO - gcc.GxxCrossSelfTestSystemEmulated.test_cross_gxx (subunit.RemotedTestCase)
2023-09-12 17:15:10,983 - oe-selftest - INFO - ... ok
2023-09-12 17:15:10,991 - oe-selftest - INFO - 7: 1/1 11/15 (773.26s) (0 failed) (gcc.GxxCrossSelfTestSystemEmulated.test_cross_gxx)
2023-09-12 17:18:06,062 - oe-selftest - INFO - gcc.GccCrossSelfTestSystemEmulated.test_cross_gcc (subunit.RemotedTestCase)
2023-09-12 17:18:06,459 - oe-selftest - INFO - ... ok
2023-09-12 17:18:06,465 - oe-selftest - INFO - 1: 1/1 12/15 (948.98s) (0 failed) (gcc.GccCrossSelfTestSystemEmulated.test_cross_gcc)
2023-09-12 17:18:45,700 - oe-selftest - INFO - gcc.GccLibGompSelfTestSystemEmulated.test_libgomp (subunit.RemotedTestCase)
2023-09-12 17:18:45,707 - oe-selftest - INFO - ... ok
2023-09-12 17:18:45,707 - oe-selftest - INFO - 3: 1/1 13/15 (988.64s) (0 failed) (gcc.GccLibGompSelfTestSystemEmulated.test_libgomp)
2023-09-12 17:27:42,846 - oe-selftest - INFO - gcc.GccLibStdCxxSelfTestSystemEmulated.test_libstdcxx (subunit.RemotedTestCase)
2023-09-12 17:27:42,884 - oe-selftest - INFO - ... ok
2023-09-12 17:27:42,884 - oe-selftest - INFO - 6: 1/1 14/15 (1525.79s) (0 failed) (gcc.GccLibStdCxxSelfTestSystemEmulated.test_libstdcxx)
2023-09-12 17:39:38,131 - oe-selftest - INFO - glibc.GlibcSelfTestSystemEmulated.test_glibc (subunit.RemotedTestCase)
2023-09-12 17:39:38,142 - oe-selftest - INFO - ... ok
2023-09-12 17:39:38,142 - oe-selftest - INFO - 8: 1/1 15/15 (2241.06s) (0 failed) (glibc.GlibcSelfTestSystemEmulated.test_glibc)
2023-09-12 17:39:38,184 - oe-selftest - INFO - ======================================================================
2023-09-12 17:39:38,184 - oe-selftest - INFO - FAIL: runqemu.QemuTest.test_qemu_can_shutdown (subunit.RemotedTestCase)
2023-09-12 17:39:38,185 - oe-selftest - INFO - ----------------------------------------------------------------------
2023-09-12 17:39:38,185 - 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 192, 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.11/unittest/case.py", line 715, in assertTrue
raise self.failureException(msg)
AssertionError: False is not true : Failed: qemux86 does not shutdown within timeout(120)
Stderr:
2023-09-12 17:02:17,059 - oe-selftest - INFO - Adding: "include selftest.inc" in /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/conf/local.conf
2023-09-12 17:02:17,059 - oe-selftest - INFO - Adding: "include bblayers.inc" in bblayers.conf
Loading cache...done.
rootfs file:
Qemu log file: /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/testimage/qemu_boot_log.20230912170429
SSH log file: /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/testimage/ssh_target_log.20230912170429
QMP Available for connection at /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/.st4uom63
Created listening socket for qemu serial console on: 127.0.0.1:49695
Created listening socket for qemu serial console on: 127.0.0.1:54179
launchcmd=runqemu nographic /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/deploy/images/qemux86/core-image-minimal-qemux86.qemuboot.conf tcpserial=49695:54179 bootparams=" printk.time=1" qemuparams="-pidfile /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/pidfile_1772097 -S -qmp unix:./.kor3bh36,server,wait -qmp unix:./.st4uom63,server,nowait"
runqemu started, pid is 2000267
waiting at most 300 seconds for qemu pid (09/12/23 17:04:31)
QMP Initializing to /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/.kor3bh36
QMP Connecting to /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/.kor3bh36
QMP connected to QEMU at 09/12/23 17:04:31 and took 0.5379478931427002 seconds
QMP released QEMU at 09/12/23 17:04:32 and took 0.07902669906616211 seconds from connect
qemu started in 0.6148955821990967 seconds - qemu procces pid is 2000318 (09/12/23 17:04:32)
Target IP: None
Server IP: None
Starting logging thread
Starting thread event loop
Connection request received
Setting connection established event
Output from runqemu:
runqemu - INFO - Using /home/pokybuild/bin/runqemu-renice to renice
runqemu - INFO - Continuing with the following parameters:
KERNEL: [/home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/deploy/images/qemux86/bzImage]
MACHINE: [qemux86]
FSTYPE: [ext4]
ROOTFS: [/home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/deploy/images/qemux86/core-image-minimal-qemux86-20230912170303.rootfs.ext4]
CONFFILE: [/home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/deploy/images/qemux86/core-image-minimal-qemux86.qemuboot.conf]
runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap0.lock failed: [Errno 11] Resource temporarily unavailable
runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap1.lock failed: [Errno 11] Resource temporarily unavailable
runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap2.lock failed: [Errno 11] Resource temporarily unavailable
runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap3.lock failed: [Errno 11] Resource temporarily unavailable
runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap4.lock failed: [Errno 11] Resource temporarily unavailable
runqemu - INFO - Using preconfigured tap device tap5
runqemu - INFO - If this is not intended, touch /tmp/qemu-tap-locks/tap5.skip to make runqemu skip tap5.
runqemu - INFO - Network configuration: ip=192.168.7.12::192.168.7.11:255.255.255.0::eth0:off:8.8.8.8
runqemu - INFO - Running /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/work/x86_64-linux/qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin/qemu-system-i386 -device virtio-net-pci,netdev=net0,mac=52:54:00:12:34:0c -netdev tap,id=net0,ifname=tap5,script=no,downscript=no -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0 -drive file=/home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/deploy/images/qemux86/core-image-minimal-qemux86-20230912170303.rootfs.ext4,if=virtio,format=raw -usb -device usb-tablet -cpu IvyBridge -machine q35 -smp 4 -m 256 -serial tcp:127.0.0.1:49695 -serial tcp:127.0.0.1:54179 -pidfile /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/pidfile_1772097 -S -qmp unix:./.kor3bh36,server,wait -qmp unix:./.st4uom63,server,nowait -serial mon:stdio -nographic -kernel /home/pokybuild/yocto-worker/qemux86/build/build-st-1772097/tmp/deploy/images/qemux86/bzImage -append 'root=/dev/vda rw ip=192.168.7.12::192.168.7.11:255.255.255.0::eth0:off:8.8.8.8 console=ttyS0 console=ttyS1 oprofile.timer=1 tsc=reliable no_timer_check rcupdate.rcu_expedited=1 printk.time=1'
runqemu - INFO - Host uptime: 88954.56
Waiting at most 1000 seconds for login banner (09/12/23 17:04:32)
Connection from 127.0.0.1:59384
Reached login banner in 60.64575529098511 seconds (09/12/23 17:05:32, 1694538332.6520703)
Logged as root in serial console
----------------------------------------------------------------------
2023-09-12 17:39:38,185 - oe-selftest - INFO - Ran 15 tests in 2242.940s
2023-09-12 17:39:38,185 - oe-selftest - INFO - FAILED
2023-09-12 17:39:38,185 - oe-selftest - INFO - (failures=1, skipped=1)
2023-09-12 17:39:43,859 - oe-selftest - INFO - RESULTS:
2023-09-12 17:39:43,860 - oe-selftest - INFO - RESULTS - binutils.BinutilsCrossSelfTest.test_binutils: PASSED (103.05s)
2023-09-12 17:39:43,860 - oe-selftest - INFO - RESULTS - binutils.BinutilsCrossSelfTest.test_gas: PASSED (112.18s)
2023-09-12 17:39:43,860 - oe-selftest - INFO - RESULTS - binutils.BinutilsCrossSelfTest.test_ld: PASSED (63.73s)
2023-09-12 17:39:43,860 - oe-selftest - INFO - RESULTS - gcc.GccCrossSelfTestSystemEmulated.test_cross_gcc: PASSED (949.38s)
2023-09-12 17:39:43,861 - oe-selftest - INFO - RESULTS - gcc.GccLibAtomicSelfTestSystemEmulated.test_libatomic: PASSED (322.08s)
2023-09-12 17:39:43,861 - oe-selftest - INFO - RESULTS - gcc.GccLibGompSelfTestSystemEmulated.test_libgomp: PASSED (988.64s)
2023-09-12 17:39:43,861 - oe-selftest - INFO - RESULTS - gcc.GccLibItmSelfTestSystemEmulated.test_libitm: PASSED (441.09s)
2023-09-12 17:39:43,861 - oe-selftest - INFO - RESULTS - gcc.GccLibStdCxxSelfTestSystemEmulated.test_libstdcxx: PASSED (1525.83s)
2023-09-12 17:39:43,861 - oe-selftest - INFO - RESULTS - gcc.GxxCrossSelfTestSystemEmulated.test_cross_gxx: PASSED (773.92s)
2023-09-12 17:39:43,861 - oe-selftest - INFO - RESULTS - glibc.GlibcSelfTestSystemEmulated.test_glibc: PASSED (2241.08s)
2023-09-12 17:39:43,861 - oe-selftest - INFO - RESULTS - meta_ide.MetaIDE.test_meta_ide_can_build_cpio_project: PASSED (46.24s)
2023-09-12 17:39:43,861 - oe-selftest - INFO - RESULTS - meta_ide.MetaIDE.test_meta_ide_can_compile_c_program: PASSED (0.81s)
2023-09-12 17:39:43,862 - oe-selftest - INFO - RESULTS - meta_ide.MetaIDE.test_meta_ide_had_installed_meta_ide_support: PASSED (0.01s)
2023-09-12 17:39:43,862 - oe-selftest - INFO - RESULTS - gcc.GccLibSspSelfTestSystemEmulated.test_libssp: SKIPPED (47.41s)
2023-09-12 17:39:43,862 - oe-selftest - INFO - RESULTS - runqemu.QemuTest.test_qemu_can_shutdown: FAILED (193.00s)
2023-09-12 17:39:46,146 - oe-selftest - INFO - SUMMARY:
2023-09-12 17:39:46,147 - oe-selftest - INFO - oe-selftest () - Ran 15 tests in 2243.606s
2023-09-12 17:39:46,147 - oe-selftest - INFO - oe-selftest - FAIL - Required tests failed (successes=13, skipped=1, failures=1, errors=0)
