We fail to start the a11y service under flatpak. Failed to talk to the accessibility service: Cannot autolaunch D-Bus without X11 $DISPLAY Could not start accessibility bus, so disabling TestWebKitAccessibility
Created attachment 438120 [details] Patch Let's try this...
Still fails :-( Failed to talk to the accessibility service: Error spawning command line ?dbus-launch --autolaunch=18a76d89e81b4cb5aa297189e9cbb201 --binary-syntax --close-stderr?: Child process exited with code 1
This seems an issue related to dbus and the configuration we currently have on the flatpak and the workers. This is what happens: 1. When the test runs it starts the dbus accessibility bus 2. For starting this it looks for an already running dbus daemon 3. On the workers it doesn't find the dbus daemon because it is not enabled for the service of the buildbot 4. Then the test it tries to auto-start dbus by using the dbus magic auto-start feature 5. On the dbus binary of the flatpak this magic is not enabled so it fails with this error "Autolaunch requested, but X11 support not compiled in. Cannot continue." So we need to either: - Option A -> Build dbus with the autostart feature inside flatpak - Option B -> Start the dbus daemon if needed on the test-runner before starting the tests - Option C -> Ensure the workers have a running dbus daemon for the buildbot service After discussing this with Carlos it seems that Option C seems the best one, as that is closer to the usual developer/user environment where dbus is assumed to be running and working. I will try to deploy this on the workers.
Comment on attachment 438120 [details] Patch This didn't fix the issue.
In the end, bots have been configured to run dbus service, so tests should be running fine now.
The fix applied on the bots caused timeouts on the layout tests. There is something weird interaction happening between flatpak and XDG_RUNTIME_DIR. This requires more investigation
The previous fix was reverted for the moment