Bug 15981

Summary: [AB-INT] xorg.XorgTest.test_xorg_running wrongfully fails
Product: [QA/Testing] Runtime Testing Reporter: Mathieu Dubois-Briand <mathieu.dubois-briand>
Component: oeqa/runtimeAssignee: Mathieu Dubois-Briand <mathieu.dubois-briand>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: Medium CC: antonin.godard, randy.macleod
Version: unspecified   
Target Milestone: 6.0   
Hardware: x86   
OS: Multiple   
Whiteboard: AB-INT
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Mathieu Dubois-Briand 2025-09-25 14:58:16 UTC
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
Comment 1 Antonin Godard 2025-09-25 15:03:24 UTC
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
Comment 2 Mathieu Dubois-Briand 2025-09-26 13:55:13 UTC
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.
Comment 3 Mathieu Dubois-Briand 2025-10-10 06:55:30 UTC
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
Comment 4 Randy MacLeod 2026-06-04 15:22:51 UTC
Added some patches to help with debugging.
Open a new bug if the underlying issue happens again.