It does help. It changes the error message to: libcolord-gtk:ERROR:cd-self-test.c:45:cd_window_get_profile_cb: assertion failed (error == NULL): failed to connect to colord: Could not connect: No such file or directory (cd_window_error, 0) FAIL cd-self-test (exit status: 134)
But of course, there's no system bus inside the chroot and colord lives on the system bus. I think this could in theory be an autopkgtest. If you compile just the test: $ gcc $(pkg-config --cflags colord-gtk) -DCD_COMPILATION cd-self-test.c $(pkg-config --libs colord-gtk) -o cd-self-test $ dbus-run-session -- xvfb-run -a ./cd-self-test [...] ERROR:cd-self-test.c:45:cd_window_get_profile_cb: assertion failed (error == NULL): no device with that property: property match 'XRANDR_name'='screen' does not exist (cd_window_error, 0) it doesn't quite work, but nearly. Maybe upstream would have an idea here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690706 Title: Tests are not being run To manage notifications about this bug go to: https://bugs.launchpad.net/colord-gtk/+bug/1690706/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
