http://autobuilder.yoctoproject.org/main/builders/nightly-qa-systemd/builds/52 Detailed log of last build step: http://autobuilder.yoctoproject.org/main/builders/nightly-qa-systemd/builds/52/steps/Running Sanity Tests_2/logs/stdio Last 60 lines of "Running Sanity Tests_2.stdio" Error log: | 51 root 79848 S /lib/systemd/systemd-journald | 69 root 0 SW [kworker/u2:2] | 76 root 29884 S /lib/systemd/systemd-udevd | 104 root 4716 S /sbin/klogd -n | 114 avahi 28004 S avahi-daemon: running [qemux86-64.local] | 116 root 21992 S /usr/sbin/ofonod -n | 117 messageb 15376 S /usr/bin/dbus-daemon --system --address=systemd: --n | 146 root 23980 S /lib/systemd/systemd-logind | 161 avahi 27880 S avahi-daemon: chroot helper | 165 root 8464 S /sbin/agetty --noclear tty1 | 176 distcc 23856 S N /usr/bin/distccd --pid-file=/var/run/distcc.pid --da | 178 distcc 23856 S N /usr/bin/distccd --pid-file=/var/run/distcc.pid --da | 189 root 35020 S /usr/sbin/connmand -n | 191 distcc 23856 S N /usr/bin/distccd --pid-file=/var/run/distcc.pid --da | 201 distcc 23856 S N /usr/bin/distccd --pid-file=/var/run/distcc.pid --da | 21 4 root 8464 S /sbin/agetty -s ttyS0 115200 vt102 | 248 root 10928 S /usr/sbin/dropbear -r /etc/dropbear/dropbear_rsa_hos | 311 root 32684 S /usr/sbin/wpa_supplicant -u | 365 root 4780 S /sbin/syslogd -n -C | 379 root 15156 S /usr/sbin/dropbear -r /etc/dropbear/dropbear_rsa_hos | 380 root 9348 S sh -c . /etc/profile; ps | 381 root 8948 R ps | | ====================================================================== | FAIL: test_vnc (oeqa.runtime.vnc.VNCTest) | ---------------------------------------------------------------------- | Traceback (most recent call last): | File "/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-qa-systemd/build/meta/lib/oeqa/utils/decorators.py", line 48, in wrapped_f | return f(*args) | File "/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-qa-systemd/build/meta/lib/oeqa/runtime/vnc.py", line 13, in test_vnc | self.assertEqua l(status , 0, msg="x11vnc server failed to start: %s" % output) | AssertionError: 1 != 0 : x11vnc server failed to start: | | ====================================================================== | FAIL: test_systemd_failed (oeqa.runtime.systemd.SystemdTests) | ---------------------------------------------------------------------- | Traceback (most recent call last): | File "/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-qa-systemd/build/meta/lib/oeqa/utils/decorators.py", line 48, in wrapped_f | return f(*args) | File "/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-qa-systemd/build/meta/lib/oeqa/runtime/systemd.py", line 24, in test_systemd_failed | self.assertEqual(status, 0, msg="Failed systemd services: %s" % self.target.run('systemctl --failed')[1]) | AssertionError: 1 != 0 : Failed systemd services: UNIT LOAD ACTIVE SUB DESCRIPTION | xserver-nodm.service loaded failed failed Xserver startup wit hout a d isplay manager | | LOAD = Reflects whether the unit definition was properly loaded. | ACTIVE = The high-level unit activation state, i.e. generalization of SUB. | SUB = The low-level unit activation state, values depend on unit type. | | 1 loaded units listed. Pass --all to see loaded but inactive units, too. | To show all installed unit files use 'systemctl list-unit-files'. | | ---------------------------------------------------------------------- | Ran 46 tests in 612.128s | | FAILED (failures=4, skipped=1) | NOTE: Sending SIGTERM to runqemu | DEBUG: Python function do_testimage finished | ERROR: Function failed: core-image-sato - FAILED - check the task log and the ssh log ERROR: Task 0 (/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-qa-systemd/build/meta/recipes-sato/images/core-image-sato.bb, do_testimage) failed with exit code '1' Summary: There was 1 ERROR message shown, returning a non-zero exit code .
More failures here: Detailed log of last build step: http://autobuilder.yoctoproject.org/main/builders/nightly-rpm/builds/33/steps/Running Sanity Tests/logs/stdio Last 60 lines of "Running Sanity Tests.stdio" Error log: | test_syslog_help (oeqa.runtime.syslog.SyslogTest) ... ok | test_syslog_running (oeqa.runtime.syslog.SyslogTest) ... ok | test_syslog_logger (oeqa.runtime.syslog.SyslogTestConfig) ... ok | test_syslog_restart (oeqa.runtime.syslog.SyslogTestConfig) ... ok | test_syslog_startup_config (oeqa.runtime.syslog.SyslogTestConfig) ... ok | test_xorg_error (oeqa.runtime.xorg.XorgTest) ... ok | test_xorg_running (oeqa.runtime.xorg.XorgTest) ... ok | test_scp_file (oeqa.runtime.scp.ScpTest) ... ok | test_vnc (oeqa.runtime.vnc.VNCTest) ... ok | test_date (oeqa.runtime.date.DateTest) ... FAIL | test_perl_exists (oeqa.runtime.perl.PerlTest) ... ok | test_perl_works (oeqa.runtime.perl.PerlTest) ... ok | test_ldd_exists (oeqa.runtime.ldd.LddTest) ... ok | test_ldd_rtldlist_check (oeqa.runtime.ldd.LddTest) ... ok | test_gcc_compile (oeqa.runtime.gcc.GccCompileTest) ... ok | test_gpp_compile (oeqa.runtime.gcc.GccCompileTest) ... ok | test_make (oe qa.runti me.gcc.GccCompileTest) ... ok | test_rpm_help (oeqa.runtime.rpm.RpmBasicTest) ... ok | test_rpm_query (oeqa.runtime.rpm.RpmBasicTest) ... ok | test_rpm_install (oeqa.runtime.rpm.RpmInstallRemoveTest) ... ok | test_rpm_remove (oeqa.runtime.rpm.RpmInstallRemoveTest) ... ok | test_smart_help (oeqa.runtime.smart.SmartBasicTest) ... ok | test_smart_info (oeqa.runtime.smart.SmartBasicTest) ... ok | test_smart_query (oeqa.runtime.smart.SmartBasicTest) ... ok | test_smart_search (oeqa.runtime.smart.SmartBasicTest) ... ok | test_smart_stats (oeqa.runtime.smart.SmartBasicTest) ... ok | test_smart_version (oeqa.runtime.smart.SmartBasicTest) ... ok | test_smart_channel (oeqa.runtime.smart.SmartRepoTest) ... ok | test_smart_channel_add (oeqa.runtime.smart.SmartRepoTest) ... ok | test_smart_channel_help (oeqa.runtime.smart.SmartRepoTest) ... ok | test_smart_channel_list (oeqa.runtime.smart.SmartRepoTest) ... ok | test_smart_channel_rpmsys (oeqa .runtime .smart.SmartRepoTest) ... ok | test_smart_channel_show (oeqa.runtime.smart.SmartRepoTest) ... ok | test_smart_install (oeqa.runtime.smart.SmartRepoTest) ... ok | test_smart_install_dependency (oeqa.runtime.smart.SmartRepoTest) ... ok | test_smart_install_from_disk (oeqa.runtime.smart.SmartRepoTest) ... ok | test_smart_install_from_http (oeqa.runtime.smart.SmartRepoTest) ... ok | test_smart_reinstall (oeqa.runtime.smart.SmartRepoTest) ... ok | test_dmesg (oeqa.runtime.dmesg.DmesgTest) ... ok | | ====================================================================== | FAIL: test_date (oeqa.runtime.date.DateTest) | ---------------------------------------------------------------------- | Traceback (most recent call last): | File "/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-rpm/build/meta/lib/oeqa/utils/decorators.py", line 48, in wrapped_f | return f(*args) | File "/home/pokybuild/yocto-autobuilder/yocto-slave/night ly-rpm/b uild/meta/lib/oeqa/runtime/date.py", line 10, in test_date | self.assertEqual(status, 0, msg="Failed to get initial date, output: %s" % output) | AssertionError: 255 != 0 : Failed to get initial date, output: | [!!! SSH command timed out after 300 seconds and it was killed] | | ---------------------------------------------------------------------- | Ran 45 tests in 1520.344s | | FAILED (failures=1) | NOTE: Sending SIGTERM to runqemu | DEBUG: Python function do_testimage finished | ERROR: Function failed: core-image-sato-sdk - FAILED - check the task log and the ssh log ERROR: Task 2 (/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-rpm/build/meta/recipes-sato/images/core-image-sato-sdk.bb, do_testimage) failed with exit code '1' Summary: There was 1 ERROR message shown, returning a non-zero exit code.
There are multiple issues here, the systemd issue is probably not something we can fix at this point for 1.5.x since it would require a systemd update, the other two issues here are likely back ports from master for issues already fixed, please try to find these patches.
I tried to reproduce the systemd issue locally but just building the image from scratch and running the tests works without any problems and no failed tests. This might be related to the entire build set and the fact that the last image is built in the same build directory as the first 2. Investigating the other issues..
Using the same build configuration I was not able to reproduce the second issue, with the "date" test failing. I believe that is a ssh timeout issue and has nothing to do with the test itself. For the record, here is the configuration for this test: Build Configuration: BB_VERSION = "1.20.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Ubuntu-14.04" TARGET_SYS = "i586-poky-linux" MACHINE = "qemux86" DISTRO = "poky" DISTRO_VERSION = "1.5.1" TUNE_FEATURES = "m32 i586" TARGET_FPU = "" meta meta-yocto meta-yocto-bsp = "(detachedfrom50e9ccb):50e9ccb2aff7b9f9dca4fda99a6832c60f64de3b" meta-qt3 = "(detachedfrom4772424):4772424ab69908d4e3b9d6d4717ca889468e6acd" I will now investigate the systemd issue in more detail and build the 3 images in the same build directory one after the other, in the same order as the autobuilder.
I just did some testing. Only the vnc test case failed. The strange thing is that if I run the commands manually via ssh, they all succeed. The latest master has no such problem. But I really don't know which commit would solve this problem. //Chen Qi
Hi Stefanx, Do you have any idea about this one? Thanks, Chen Qi
Chen Qi, can you please paste your output of log.do_testimage? Thanks! :)
(In reply to comment #7) > Chen Qi, can you please paste your output of log.do_testimage? Thanks! :) DEBUG: Executing python function do_testimage_auto NOTE: Created listening socket for qemu serial console on: 127.0.0.1:34386 NOTE: DISPLAY value: localhost:11.0 NOTE: rootfs file: /home/chenqi/poky/build-dora-systemd/tmp/work/qemux86-poky-linux/core-image-sato-sdk/1.0-r0/testimage/core-image-sato-sdk-qemux86-testimage.ext3 NOTE: Qemu log file: /home/chenqi/poky/build-dora-systemd/tmp/work/qemux86-poky-linux/core-image-sato-sdk/1.0-r0/testimage/qemu_boot_log.20140428054941 NOTE: SSH log file: /home/chenqi/poky/build-dora-systemd/tmp/work/qemux86-poky-linux/core-image-sato-sdk/1.0-r0/testimage/ssh_target_log.20140428054941 NOTE: runqemu started, pid is 11451 NOTE: waiting at most 60 seconds for qemu pid NOTE: qemu started - qemu procces pid is 11505 NOTE: IP found: 192.168.7.2 NOTE: Waiting at most 1000 seconds for login banner NOTE: Connection from 127.0.0.1:52222 NOTE: Reached login banner NOTE: Test modules ['oeqa.runtime.ping', 'oeqa.runtime.ssh', 'oeqa.runtime.vnc'] NOTE: Found 3 tests test_ping (oeqa.runtime.ping.PingTest) ... ok test_ssh (oeqa.runtime.ssh.SshTest) ... ok test_vnc (oeqa.runtime.vnc.VNCTest) ... FAIL ====================================================================== FAIL: test_vnc (oeqa.runtime.vnc.VNCTest) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/chenqi/poky/meta/lib/oeqa/utils/decorators.py", line 48, in wrapped_f return f(*args) File "/home/chenqi/poky/meta/lib/oeqa/runtime/vnc.py", line 19, in test_vnc self.assertEqual(status, 0, msg="x11vnc server not running on port %s\n\n%s" % (vncport, self.target.run('netstat -ntl; cat x11vnc.log')[1])) AssertionError: 1 != 0 : x11vnc server not running on port 5900 Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 0.0.0.0:6000 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN tcp 0 0 :::6000 :::* LISTEN tcp 0 0 ::1:53 :::* LISTEN tcp 0 0 :::22 :::* LISTEN ############################################################### #@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@# #@ @# #@ ** WARNING ** WARNING ** WARNING ** WARNING ** @# #@ @# #@ YOU ARE RUNNING X11VNC WITHOUT A PASSWORD!! @# #@ @# #@ This means anyone with network access to this computer @# #@ may be able to view and control your desktop. @# #@ @# #@ >>> If you did not mean to do this Press CTRL-C now!! <<< @# #@ @# #@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@# #@ @# #@ You can create an x11vnc password file by running: @# #@ @# #@ x11vnc -storepasswd password /path/to/passfile @# #@ or x11vnc -storepasswd /path/to/passfile @# #@ or x11vnc -storepasswd @# #@ @# #@ (the last one will use ~/.vnc/passwd) @# #@ @# #@ and then starting x11vnc via: @# #@ @# #@ x11vnc -rfbauth /path/to/passfile @# #@ @# #@ an existing ~/.vnc/passwd file from another VNC @# #@ application will work fine too. @# #@ @# #@ You can also use the -passwdfile or -passwd options. @# #@ (note -passwd is unsafe if local users are not trusted) @# #@ @# #@ Make sure any -rfbauth and -passwdfile password files @# #@ cannot be read by untrusted users. @# #@ @# #@ Use x11vnc -usepw to automatically use your @# #@ ~/.vnc/passwd or ~/.vnc/passwdfile password files. @# #@ (and prompt you to create ~/.vnc/passwd if neither @# #@ file exists.) Under -usepw, x11vnc will exit if it @# #@ cannot find a password to use. @# #@ @# #@ @# #@ Even with a password, the subsequent VNC traffic is @# #@ sent in the clear. Consider tunnelling via ssh(1): @# #@ @# #@ http://www.karlrunge.com/x11vnc/#tunnelling @# #@ @# #@ Or using the x11vnc SSL options: -ssl and -stunnel @# #@ @# #@ Please Read the documention for more info about @# #@ passwords, security, and encryption. @# #@ @# #@ http://www.karlrunge.com/x11vnc/faq.html#faq-passwd @# #@ @# #@ To disable this warning use the -nopw option, or put @# #@ 'nopw' on a line in your ~/.x11vncrc file. @# #@ @# #@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@# ############################################################### 28/04/2014 05:53:19 x11vnc version: 0.9.13 lastmod: 2011-08-10 pid: 346 28/04/2014 05:53:19 Using X display :0 28/04/2014 05:53:19 rootwin: 0x43 reswin: 0x1000001 dpy: 0x8410ea0 28/04/2014 05:53:19 28/04/2014 05:53:19 ------------------ USEFUL INFORMATION ------------------ 28/04/2014 05:53:19 X DAMAGE available on display, using it for polling hints. 28/04/2014 05:53:19 To disable this behavior use: '-noxdamage' 28/04/2014 05:53:19 28/04/2014 05:53:19 Most compositing window managers like 'compiz' or 'beryl' 28/04/2014 05:53:19 cause X DAMAGE to fail, and so you may not see any screen 28/04/2014 05:53:19 updates via VNC. Either disable 'compiz' (recommended) or 28/04/2014 05:53:19 supply the x11vnc '-noxdamage' command line option. 28/04/2014 05:53:19 28/04/2014 05:53:19 Wireframing: -wireframe mode is in effect for window moves. 28/04/2014 05:53:19 If this yields undesired behavior (poor response, painting 28/04/2014 05:53:19 errors, etc) it may be disabled: 28/04/2014 05:53:19 - use '-nowf' to disable wireframing completely. 28/04/2014 05:53:19 - use '-nowcr' to disable the Copy Rectangle after the 28/04/2014 05:53:19 moved window is released in the new position. 28/04/2014 05:53:19 Also see the -help entry for tuning parameters. 28/04/2014 05:53:19 You can press 3 Alt_L's (Left "Alt" key) in a row to 28/04/2014 05:53:19 repaint the screen, also see the -fixscreen option for 28/04/2014 05:53:19 periodic repaints. 28/04/2014 05:53:19 28/04/2014 05:53:19 XFIXES available on display, resetting cursor mode 28/04/2014 05:53:19 to: '-cursor most'. 28/04/2014 05:53:19 to disable this behavior use: '-cursor arrow' 28/04/2014 05:53:19 or '-noxfixes'. 28/04/2014 05:53:19 using XFIXES for cursor drawing. 28/04/2014 05:53:19 GrabServer control via XTEST. Xlib: extension "RECORD" missing on display ":0". 28/04/2014 05:53:19 28/04/2014 05:53:19 The RECORD X extension was not found on the display. 28/04/2014 05:53:19 If your system has disabled it by default, you can 28/04/2014 05:53:19 enable it to get a nice x11vnc performance speedup 28/04/2014 05:53:19 for scrolling by putting this into the "Module" section 28/04/2014 05:53:19 of /etc/X11/xorg.conf or /etc/X11/XF86Config: 28/04/2014 05:53:19 28/04/2014 05:53:19 Section "Module" 28/04/2014 05:53:19 ... 28/04/2014 05:53:19 Load "record" 28/04/2014 05:53:19 ... 28/04/2014 05:53:19 EndSection 28/04/2014 05:53:19 28/04/2014 05:53:19 28/04/2014 05:53:19 XKEYBOARD: number of keysyms per keycode 7 is greater 28/04/2014 05:53:19 than 4 and 51 keysyms are mapped above 4. 28/04/2014 05:53:19 Automatically switching to -xkb mode. 28/04/2014 05:53:19 If this makes the key mapping worse you can 28/04/2014 05:53:19 disable it with the "-noxkb" option. 28/04/2014 05:53:19 Also, remember "-remap DEAD" for accenting characters. 28/04/2014 05:53:19 28/04/2014 05:53:19 X FBPM extension not supported. 28/04/2014 05:53:19 X display is not capable of DPMS. 28/04/2014 05:53:19 -------------------------------------------------------- 28/04/2014 05:53:19 28/04/2014 05:53:19 Default visual ID: 0x21 28/04/2014 05:53:19 Read initial data from X display into framebuffer. 28/04/2014 05:53:19 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/2560 28/04/2014 05:53:19 28/04/2014 05:53:19 X display :0 is 32bpp depth=24 true color 28/04/2014 05:53:19 28/04/2014 05:53:19 Autoprobing TCP port 28/04/2014 05:53:19 Autoprobing selected port 5900 28/04/2014 05:53:19 Listening also on IPv6 port 5900 (socket 6) 28/04/2014 05:53:19 Xinerama: Library libXinerama is not available to determine 28/04/2014 05:53:19 Xinerama: the head geometries, consider using -blackout 28/04/2014 05:53:19 Xinerama: if the screen is non-rectangular. 28/04/2014 05:53:19 fb read rate: 23 MB/sec 28/04/2014 05:53:19 The X server says there are 13 mouse buttons. 28/04/2014 05:53:19 screen setup finished. 28/04/2014 05:53:19 28/04/2014 05:53:19 WARNING: You are running x11vnc WITHOUT a password. See 28/04/2014 05:53:19 WARNING: the warning message printed above for more info. 28/04/2014 05:53:19 The VNC desktop is: qemux86:0 ****************************************************************************** Have you tried the x11vnc '-ncache' VNC client-side pixel caching feature yet? The scheme stores pixel data offscreen on the VNC viewer side for faster retrieval. It should work with any VNC viewer. Try it by running: x11vnc -ncache 10 ... One can also add -ncache_cr for smooth 'copyrect' window motion. More info: http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching 28/04/2014 05:53:19 check_xrandr_event(): 28/04/2014 05:53:19 Detected XRANDR event at location 'check_xevents': caught signal: 15 28/04/2014 05:53:19 deleted 20 tile_row polling images. ---------------------------------------------------------------------- Ran 3 tests in 64.847s FAILED (failures=1) NOTE: Sending SIGTERM to runqemu DEBUG: Python function do_testimage_auto finished ERROR: Function failed: core-image-sato-sdk - FAILED - check the task log and the ssh log
(In reply to comment #7) > Chen Qi, can you please paste your output of log.do_testimage? Thanks! :) I only enabled 'ping', 'ssh' and 'vnc' so that the testing process would take less time. If I logged onto the target and typed the commands manually, everything seems fine. See the logs below. chenqi@pek-hostel-vm07:~ [0] $ ssh root@192.168.7.2 root@qemux86:~# x11vnc -display :0 -bg -o x11vnc.log PORT=5900 root@qemux86:~# echo $? 0 root@qemux86:~# netstat -ntl | grep ":5900" tcp 0 0 0.0.0.0:5900 0.0.0.0:* LISTEN tcp 0 0 :::5900 :::* LISTEN root@qemux86:~# echo $? 0 root@qemux86:~# netstat -ntl Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 0.0.0.0:5900 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:6000 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN tcp 0 0 :::5900 :::* LISTEN tcp 0 0 :::6000 :::* LISTEN tcp 0 0 ::1:53 :::* LISTEN tcp 0 0 :::22 :::* LISTEN
The problem you are encountering is a different one. In the autobuilder tests, X failed to start. Your tests just failed somewhow to start the vnc server, but X was running (28/04/2014 05:53:19 X display :0 is 32bpp depth=24 true color).
I built the 3 image types and ran the tests for them but I could not reproduce the issue. Here are the configurations for the 3 builds(core-image-sato) in the autobuilder order: 1) MACHINE = "qemux86-64" DISTRO_FEATURES_append = " systemd" VIRTUAL-RUNTIME_init_manager = "systemd" INHERIT += "testimage" TEST_SUITES_append = " systemd" 2) MACHINE = "qemux86-64" DISTRO_FEATURES_append = " systemd" VIRTUAL-RUNTIME_init_manager = "sysvinit" 3) MACHINE = "qemux86-64" DISTRO_FEATURES_append = " systemd" VIRTUAL-RUNTIME_init_manager = "systemd" DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit" INHERIT += "testimage" TEST_SUITES_append = " systemd"
(In reply to comment #10) > The problem you are encountering is a different one. In the autobuilder > tests, X failed to start. Your tests just failed somewhow to start the vnc > server, but X was running (28/04/2014 05:53:19 X display :0 is 32bpp > depth=24 true color). Do you have any idea which parts in oeqa codes would possibly have impacts on the behavior? As I commented above, if I start the target with `runqemu qemux86' and run the commands manually, there would be no problem. The automatic testing is always failing the vnc test case. Do you have any clue which part in oeqa may be responsible for this? Thanks， Chen Qi
(In reply to comment #11) > I built the 3 image types and ran the tests for them but I could not > reproduce the issue. > > Here are the configurations for the 3 builds(core-image-sato) in the > autobuilder order: > 1) > MACHINE = "qemux86-64" > > DISTRO_FEATURES_append = " systemd" > VIRTUAL-RUNTIME_init_manager = "systemd" > > INHERIT += "testimage" > TEST_SUITES_append = " systemd" > > 2) > MACHINE = "qemux86-64" > > DISTRO_FEATURES_append = " systemd" > VIRTUAL-RUNTIME_init_manager = "sysvinit" > > 3) > MACHINE = "qemux86-64" > > DISTRO_FEATURES_append = " systemd" > VIRTUAL-RUNTIME_init_manager = "systemd" > DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit" > > INHERIT += "testimage" > TEST_SUITES_append = " systemd" Are you testing on the dora branch? Best Regards, Chen Qi
Please note that 1.5.2 RC3 did not fail these tests. We can look for the commits added or maybe it cannot be reproduced. In your case we have to investigate. Can you please give us your build configuration and commits? also the Linux Distro you are using. Thank you!
The specified test cannot be reproduced as described and they all passed for 1.5.2 RC3 . Please note that the issue Qi mentioned is not related to the AB ones. That specific issue is about systemd + openssh not disowning the child processes when a ssh session ends and it appears to be as intended for systemd. Also the AB tests use core-image-sato with dropbear and do not have this issue. If this is indeed an issue, a new bug should be opened. Closing this as WORKSFORME.