15981 2025-09-25 14:58:16 +0000 [AB-INT] xorg.XorgTest.test_xorg_running wrongfully fails 2026-06-04 15:22:51 +0000 1 1 10 QA/Testing Runtime Testing oeqa/runtime unspecified x86 Multiple RESOLVED INVALID AB-INT Medium normal 6.0 1 mathieu.dubois-briand mathieu.dubois-briand antonin.godard randy.macleod --- --- No (bug/feature does not impact docs) oldest_to_newest 102824 0 mathieu.dubois-briand 2025-09-25 14:58:16 +0000 We have recently seen a test fail, complaining about xorg not being running, while actually it is. Traceback (most recent call last): File "/srv/pokybuild/yocto-worker/pkgman-non-rpm/build/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f return func(*args, **kwargs) File "/srv/pokybuild/yocto-worker/pkgman-non-rpm/build/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f return func(*args, **kwargs) File "/srv/pokybuild/yocto-worker/pkgman-non-rpm/build/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f return func(*args, **kwargs) File "/srv/pokybuild/yocto-worker/pkgman-non-rpm/build/meta/lib/oeqa/runtime/cases/xorg.py", line 23, in test_xorg_running self.assertEqual(status, 0, msg=msg) AssertionError: 255 != 0 : Xorg does not appear to be running UID PID PPID C STIME TTY TIME CMD ... root 512 1 0 01:33 ? 00:00:00 xinit /etc/X11/Xsession -- /usr/bin/Xorg :0 -br -pn root 527 512 14 01:33 ? 00:05:43 /usr/bin/Xorg :0 -br -pn pkgman-non-rpm ubuntu2204-vk-2 master completed at 2025-09-20 02:50:34+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/67/builds/2443/steps/18/logs/stdio 102827 1 antonin.godard 2025-09-25 15:03:24 +0000 Exit code is 255 which doesn't match grep's exit codes https://www.gnu.org/software/grep/manual/grep.html#Exit-Status-1 Maybe an SSH connection issue? https://www.man7.org/linux/man-pages/man1/ssh.1.html#EXIT_STATUS > ssh exits with the exit status of the remote command or with 255 if an error occurred. Not sure how commands are sent to the target though, I just assumed SSH 102837 2 mathieu.dubois-briand 2025-09-26 13:55:13 +0000 Having a look at procps source code, I can't see any way it would have exited with value 255. So this seems to confirm an SSH failure. It would be great if we knew why SSH is failing, but it runs with "-o LogLevel=ERROR", so we probably miss some info. I will try to run it with default loglevel, if it does not break all tests maybe we should do it that way. Also, we should probably add an extra log line when the SSH exit code is 255. 102908 3 mathieu.dubois-briand 2025-10-10 06:55:30 +0000 We merged some patch, failing test with SSH output when SSH does fail. This will not fix the underlying issue of this ticket, as the root cause it still not known, but should help to investigate. https://git.openembedded.org/openembedded-core/commit/?id=afe118d4f2de 105719 4 randy.macleod 2026-06-04 15:22:51 +0000 Added some patches to help with debugging. Open a new bug if the underlying issue happens again.