You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[shared-ci] E2E — composed common suite / e2e / GNOME — common failing across projectbluefin/common #1688
Summary: The E2E — composed common suite / e2e / GNOME — common check is failing on 4 open pull requests in projectbluefin/common at the same time. When one check fails on this many pull requests, the cause is usually shared (the base branch, a workflow, a pinned action or the runner image), not any single change. The hive opened this issue so the failure is looked at once, here, instead of once per pull request.
Evidence
Check: E2E — composed common suite / e2e / GNOME — common
Default branch: the newest run of this check on the pull requests' base branch is red too.
Log excerpt from the failing runs:
Cached apt install unusable; refreshing from Ubuntu mirrors.
Process completed with exit code 1.
Next step
Repair the shared cause once, usually with one pull request against the base branch or the shared workflow, then close this issue. Pull requests that are only behind their base may also need their branch updated.
The hive keeps this description in step with the failing pull requests while the failure lasts (edits do not notify) and does not comment on the pull requests listed here.
Next action: a triager or maintainer reviews this issue.
Reporter or contributor
If no kind/* label is set, categorize the issue with one of: /kind bug, /kind regression, /kind security, /kind feature, /kind documentation or /kind cleanup.
Optionally add an area with /area <area> if this repository supports area labels; use a value from its label list.
Triager or maintainer
Review the report and ask the reporter for any missing information.
When the scope is accepted and the issue is ready for work, comment /triage accepted. Only triagers and maintainers can do this; acceptance does not assign an implementer.
needs-kind clears when a kind is set. needs-triage and this post clear when triage is accepted.
Summary: the shared cause is #1687, which merged at 2:49 PM EST and switched PR E2E from bluefin:testing to Dakota. Every PR run since then fails the same 14 common-suite scenarios on dakota-common. The "cached apt install" line in the excerpt is a warning, not the cause. None of #1674, #1684 or #1685 is at fault: all three are up to date with main (3a03703), and their failure lists are identical.
Before (bluefin:testing, e.g. run 43632403805 at 2:29 PM): 53 passed, 0 failed. The job went red on a known SELinux denial (mac_admin, chcon, tuned_t).
xdg-desktop-portal-gnome and document portal inactive; D-Bus Timeout was reached
user session not running, or a real Dakota gap
What's needed. This is not one mechanical fix. Each group needs a decision on whether Dakota or the test is wrong:
The rpm-ostree check, and probably the Ptyxis path, should become Dakota-aware in testsuite.
The portal group should be checked by hand on a Dakota testing VM before anyone skips it, because nine inactive portal services could be a real user-facing bug.
The PR E2E check is not required on main (the required checks are validate and the two image builds), so these failures don't block merges. They do turn every PR's E2E red, which hides real regressions.
Hi! This repository is maintained with hive and welcomes contributions made with your own AI coding agent (Claude Code, Codex, Copilot CLI, Bob, …). hosted-projectbluefin-knuckle-gjvq picked this issue as a good place to start because:
Fork or branch, make the change with your agent, and sign each commit with DCO (git commit -s).
Open a PR whose description says Fixes #1688 — that closing keyword is how hive's contributor lane links the PR to your claim.
Hive runs CI and merges green PRs from claimed contributors automatically.
Paste this to your agent
Fix #1688 in github.com/projectbluefin/common (https://github.com/projectbluefin/common/issues/1688). First open https://hosted-projectbluefin-common-nmq5.hive.hivecommons.dev/contribute?issue=projectbluefin%2Fcommon%231688 and claim the issue through the hive relay (sign in with GitHub). Work on a fork/branch; keep the change scoped to the issue; sign every commit with DCO (git commit -s); open a PR whose description contains the line 'Fixes #1688' so the hive's contributor lane can auto-merge it once CI is green. Read and follow https://github.com/projectbluefin/common/blob/HEAD/AGENTS.md before changing code.
Prefer not to drive the loop by hand? Run your own hive (we call them clankers) — a relay on your machine that claims, opens the PR and handles review fixes for you, and earns you a contributor profile and a leaderboard place: see https://hosted-projectbluefin-common-nmq5.hive.hivecommons.dev/contribute.
Activity
github-actions commentedon Nov 15, 2026
Issue triage
Next action: a triager or maintainer reviews this issue.
Reporter or contributor
kind/*label is set, categorize the issue with one of:/kind bug,/kind regression,/kind security,/kind feature,/kind documentationor/kind cleanup./area <area>if this repository supports area labels; use a value from its label list.Triager or maintainer
/triage accepted. Only triagers and maintainers can do this; acceptance does not assign an implementer.needs-kindclears when a kind is set.needs-triageand this post clear when triage is accepted.See Triage & Prow Commands for all available commands.
Danathar commentedon Nov 15, 2026
Summary: the shared cause is #1687, which merged at 2:49 PM EST and switched PR E2E from
bluefin:testingto Dakota. Every PR run since then fails the same 14 common-suite scenarios ondakota-common. The "cached apt install" line in the excerpt is a warning, not the cause. None of #1674, #1684 or #1685 is at fault: all three are up to date with main (3a03703), and their failure lists are identical.Before and after #1687
mac_admin, chcon, tuned_t).The 14 failures, from
results.jsonin run 43653470297. The scenarios live in projectbluefin/testsuitetests/common/features/.common_immutable.feature:13)sudo: 'rpm-ostree': command not foundcommon_dconf.feature:76)/usr/bin/xdg-terminal-exec, test expectsxdg-terminal-execcommon_dconf.feature:89)['<Super>space']common_desktop_entries.feature:12,24)common_portals.feature:25,29;portal_integration.feature:10,14,18,22,26,30,38xdg-desktop-portal-gnomeand document portalinactive; D-BusTimeout was reachedWhat's needed. This is not one mechanical fix. Each group needs a decision on whether Dakota or the test is wrong:
The
PR E2Echeck is not required on main (the required checks arevalidateand the two image builds), so these failures don't block merges. They do turn every PR's E2E red, which hides real regressions.hivecommons-hive commentedon Nov 15, 2026
🌱 Good first issue — bring your own coding agent
Hi! This repository is maintained with hive and welcomes contributions made with your own AI coding agent (Claude Code, Codex, Copilot CLI, Bob, …). hosted-projectbluefin-knuckle-gjvq picked this issue as a good place to start because:
How to land it (no waiting on a human):
git commit -s).Fixes #1688— that closing keyword is how hive's contributor lane links the PR to your claim.Paste this to your agent
Prefer not to drive the loop by hand? Run your own hive (we call them clankers) — a relay on your machine that claims, opens the PR and handles review fixes for you, and earns you a contributor profile and a leaderboard place: see https://hosted-projectbluefin-common-nmq5.hive.hivecommons.dev/contribute.
If nobody claims it, hive may pick it up itself — claiming first prevents that. Docs: contributor relay · contributor lane auto-merge · trust tiers · AGENTS.md.
119 remaining items
test(common): make rpm-ostree and Ptyxis keybinding checks Dakota-awa…
docs(e2e): update e2e-ci skill for Dakota base and candidate composition
docs: update workflow-map and lab-testing for composed Dakota post-me…
test(motd): run uwelcome.sh tests under pty for tty guard
fix(dakota): align common testing workflows and E2E lanes
test(motd): run uwelcome.sh tests under pty for tty guard
test(motd): run uwelcome.sh tests under pty for tty guard
fix(dakota): align common testing workflows and E2E lanes