Created attachment 861054 [details] build.log Caught on amd64 container on devbox. This container was fully depcleaned yesterday, so it is quite clean from packages. Seems like "gphoto2" is missing from test deps. util/umockdev-0.17.17/work/umockdev-0.17.17/src/umockdev-wrapper /var/tmp/portage/dev-util/umockdev-0.17.17/work/umockdev-0.17.17-abi_x86_64.amd64/test-umockdev-run ――――――――――――――――――――――――――――――――――――― ✀ ――――――――――――――――――――――――――――――――――――― stdout: # random seed: R02S6a5c7c4f90583a0c47889bd5ca2049a3 1..16 # Start of umockdev-run tests ok 1 /umockdev-run/exit_code ok 2 /umockdev-run/version ok 3 /umockdev-run/pipes ok 4 /umockdev-run/udevadm-block ok 5 /umockdev-run/invalid-args ok 6 /umockdev-run/invalid-device [SKIP: gphoto2 not installed] [SKIP: gphoto2 not installed] [SKIP: gphoto2 not installed] [SKIP: gphoto2 not installed] ok 7 /umockdev-run/invalid-ioctl Bail out! FATAL-ERROR: test-umockdev-run.vala:56: 'Cannot install /non/existing for device /dev/input/event5:' not found in ' ** (umockdev-run:218): ERROR **: 17:52:57.335: umockdev.vala:1428: umockdev Testbed.create_node_for_device: openpty() failed: No such file or directory ' stderr: sh: line 1: type: gphoto2: not found sh: line 1: type: gphoto2: not found sh: line 1: type: gphoto2: not found sh: line 1: type: gphoto2: not found
I think the lack of gphoto2 is causing the `/umockdev-run/integration/gphoto-detect` test to skip. The actual failure appears to be from a different subtest: Bail out! FATAL-ERROR: test-umockdev-run.vala:56: 'Cannot install /non/existing for device /dev/input/event5:' not found in '** (umockdev-run:218): ERROR **: 17:52:57.335: umockdev.vala:1428: umockdev Testbed.create_node_for_device: openpty() failed: No such file or directory' For my future self, the integration tests have these dependencies: /umockdev-run/integration/gphoto-detect - media-gfx/gphoto2 /umockdev-run/integration/input-touchpad - x11-drivers/xf86-video-dummy - x11-drivers/xf86-input-synaptics /umockdev-run/integration/input-evtest* - app-misc/evtest I don't really know if we should require them or not. But it would be frustrating to see a failure and not be able to reproduce it because you're lacking a dep (which might be happening here somehow).
Looks like your specific failure comes from tests/test-umockdev-run.vala:t_run_invalid_script() > // nonexisting script > check_program_error ("true", "-d " + rootdir + > "/devices/input/usbkbd.umockdev -s " + > "/dev/input/event5=/non/existing -- true", > "Cannot install /non/existing for device /dev/input/event5:"); I wonder if this could be another missing x11-driver? x11-drivers/xf86-input-libinput is the only driver I have installed (other than dummy and synaptics that I installed for this testing) When I uninstall xf86-input-libinput, I get a different failure: > # DEBUG: test-umockdev-run.vala:595: failed to clean up /tmp/.X5-lock: No such file or directory > not ok /umockdev-run/integration/input-touchpad - FATAL-ERROR: umockdev-> utils.vala:16: cannot remove /tmp/.X11-unix/X5: No such file or directory Bail out!
Created attachment 892265 [details] umockdev-0.18.1.ebuild Running the tests as Debian does look to allow tests to pass. In summary, we would need to add the extra deps, set longer timeouts, and run tests in serial. Attached ebuild does that and works for me... but I still don't understand why running MAKEOPTS="-j1" meson_src_test keeps failing, while running plain meson succeeds :/
