Created attachment 1664733 [details] logs We use those as a part of gating, might be good to get them working. Version-Release number of selected component (if applicable): flatpak-1.6.2-1.el8.x86_64 How reproducible: always Steps to Reproduce: 1.Download srpm 2.build flatpak 3.run make check Actual results: ERROR: tests/test-update-portal.sh - too few tests run (expected 6, got 0) ERROR: tests/test-update-portal.sh - exited with status 1
Still can be reproduced with flatpak-1.8.5-1.el8.x86_64
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
The failure is: Error creating proxy: Error calling StartServiceByName for org.freedesktop.portal.Flatpak: Timeout was reached ... and it is coming from tests/test-update-portal.c: connection = g_bus_get_sync (G_BUS_TYPE_SESSION, NULL, &error); if (connection == NULL) { g_printerr ("Error connecting: %s\n", error->message); return 1; } portal = portal_flatpak_proxy_new_sync (connection, G_DBUS_PROXY_FLAGS_NONE, portal_name, portal_path, NULL, &error); if (portal == NULL) { g_printerr ("Error creating proxy: %s\n", error->message); return 1; }
Something is wrong with the D-Bus set-up in the test environment. I see that in RHEL 8, Flatpak doesn't use xdg-dbus-proxy, but it's own built-in flatpak-dbus-proxy, so that's not it. Is dbus-daemon installed there? Could you please try to strace the test-update-portal helper binary by doing something like this in tests/test-update-portal.sh: -run_with_sandboxed_bus ${test_builddir}/test-update-portal monitor monitor.pid > update-monitor.out +run_with_sandboxed_bus strace -oslog ${test_builddir}/test-update-portal monitor monitor.pid > update-monitor.out