Another new AB-INT seen on the autobuilder. I don't know why SSH returned exist status 255, as the connection succeed at least partially: the "failed to create display" string comes from wayland-info. https://gitlab.freedesktop.org/wayland/wayland-utils/-/blob/main/wayland-info/wayland-info.c?ref_type=heads#L3240 Traceback (most recent call last): File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/layers/openembedded-core/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f return func(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^ File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/layers/openembedded-core/meta/lib/oeqa/runtime/cases/weston.py", line 58, in test_wayland_info status, output = self.target.run(command) ^^^^^^^^^^^^^^^^^^^^^^^^ File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/layers/openembedded-core/meta/lib/oeqa/core/target/ssh.py", line 98, in run status, output = self._run(sshCmd, processTimeout, ignore_status, raw, ignore_ssh_fails) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/layers/openembedded-core/meta/lib/oeqa/core/target/ssh.py", line 70, in _run raise AssertionError("ssh exited with status '255' for command " AssertionError: ssh exited with status '255' for command '['ssh', '-l', 'root', '-o', 'ServerAliveCountMax=2', '-o', 'ServerAliveInterval=30', '-o', 'UserKnownHostsFile=/dev/null', '-o', 'StrictHostKeyChecking=no', '-o', 'LogLevel=ERROR', '192.168.7.2', 'export PATH=/usr/sbin:/sbin:/usr/bin:/bin; export XDG_RUNTIME_DIR=/run/user/`id -u weston`; export WAYLAND_DISPLAY=wayland-1; wayland-info']': this is likely an SSH failure failed to create display: No such file or directory Traceback (most recent call last): File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/layers/openembedded-core/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f return func(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^ File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/layers/openembedded-core/meta/lib/oeqa/runtime/cases/weston.py", line 63, in test_weston_can_initialize_new_wayland_compositor existing_wl_processes = self.get_processes_of('weston-desktop-shell', 'existing') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/layers/openembedded-core/meta/lib/oeqa/runtime/cases/weston.py", line 28, in get_processes_of self.assertEqual(status, 0, msg='Retrieve %s (%s) processes error: %s' % (target, error_msg, output)) AssertionError: 1 != 0 : Retrieve weston-desktop-shell (existing) processes error: Traceback (most recent call last): File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/layers/openembedded-core/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f return func(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^ File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/layers/openembedded-core/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f return func(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^ File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/layers/openembedded-core/meta/lib/oeqa/runtime/cases/weston.py", line 24, in test_weston_running self.assertEqual(status, 0, msg=msg) AssertionError: 1 != 0 : Weston does not appear to be running PID USER VSZ STAT COMMAND
oe-selftest-armhost ubuntu2404-vk-arm2 mathieu/master-next completed at 2025-12-10 11:14:58+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/2949/steps/15/logs/stdio
Created attachment 5159 [details] qemu boot log Attaching boot log, we have some seats errors in there: ^MINIT: Entering runlevel: 5 Configuring network interfaces... ip: RTNETLINK answers: File exists Starting system message bus: dbus. 00:00:00.000 ESC[1;34m [9.1/seatd/seat.c:48] Created VT-bound seat seat0ESC[0m 00:00:00.000 ESC[1;34m [9.1/seatd/seatd.c:194] seatd startedESC[0m Starting Dropbear SSH server: dropbear. Starting rpcbind daemon...done. Starting bluetooth: bluetoothd. Starting syslogd/klogd: done * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon ...done. 00:00:01.293 ESC[1;34m [9.1/seatd/server.c:145] New client connected (pid: 351, uid: 1000, gid: 1000)ESC[0m 00:00:01.293 ESC[1;34m [9.1/seatd/seat.c:239] Added client 2 to seat0ESC[0m 00:00:01.354 ESC[1;34m [9.1/seatd/seat.c:563] Opened client 2 on seat0ESC[0m 00:00:01.364 ESC[1;34m [9.1/seatd/seat.c:606] Disabling client 2 on seat0ESC[0m 00:00:01.382 ESC[1;31m [9.1/seatd/seat.c:327] Could open device: client is not activeESC[0m 00:00:01.390 ESC[1;31m [9.1/seatd/client.c:229] Could not open device: Operation not permittedESC[0m 00:00:01.391 ESC[1;34m [9.1/seatd/seat.c:158] No clients on seat0 to activateESC[0m seatd: /usr/src/debug/seatd/0.9.1/common/terminal.c:136: get_tty_path: Assertion `tty >= 0' failed. 00:00:00.098 ESC[1;31m [9.1/libseat/backend/seatd.c:311] Could not poll connection: Broken pipeESC[0m 00:00:00.099 ESC[1;31m [9.1/libseat/backend/seatd.c:131] Invalid message: insufficient data receivedESC[0m Internal warning: debug scope 'drm-backend' has not been destroyed.
Wondering if this is related to the systemd upgrade that just landed, which included a change to xserver-nodm to mitigate a device race...
If we didn't see this since the initial report which was on master-next then I blame the systemd upgrade which wasn't complete.