Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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
Comment 4RHEL Program Management
2021-08-21 07:26:57 UTC
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.
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
Comment 11RHEL Program Management
2022-07-26 07:27:47 UTC
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.
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