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-a failing across projectbluefin/common #1680
Summary: The E2E — composed common suite / e2e / GNOME — common-a check is failing on 3 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-a
Default branch: the newest run of this check on the base branch is not red. Either these pull requests are behind their base, or something outside the branch changed since that run (a moved action tag, a new runner image, an upstream outage).
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.
Same cause as #1679: all scenarios pass (53 passed, 0 failed), and the SELinux denial gate fails on { mac_admin } comm=chcon tuned_t. Details and options are in #1679 .
Good first issue — withdrawn by hosted-projectbluefin-knuckle-gjvq: this issue is not open to new contributors — it carries the blocked label, so it cannot be worked right now. The good first issue and help wanted labels have been removed (2026-11-14T14:50:14Z). Sorry for the noise! Issues open to new contributors are listed on the relay page: https://hosted-projectbluefin-common-nmq5.hive.hivecommons.dev/contribute
Summary: One group of this project's desktop tests (the "common-a" group) keeps failing on pull requests. The tests themselves pass. What fails is a later check that stops on any security warning the system logs while running. That warning comes from the old, frozen system image the tests start from, not from anything in this repository. Moving to a newer starting image only helps after a related fix in another project (#1203 in the utah repository) is merged and built. Until then, no change here can turn this check green.
Not something this repo can fix. The tuned_t domain comes from the base image. On main, .github/workflows/pr-e2e.yml sets BASE_IMAGE: ghcr.io/projectbluefin/bluefin:testing, and that image was last built from the archived projectbluefin/bluefin repo. This repo ships no tuned config, and it only runs chcon in just overlay, which is a developer recipe, not part of the image.
Why the obvious change doesn't help yet. Pointing BASE_IMAGE at ghcr.io/projectbluefin/utah:testing would hit the same mac_admin/chcon class of denial today. fix(selinux): stop two harmless security warnings on every boot utah#1203 (open, not merged) fixes that. The repoint should land after that PR merges and a new utah :testing image is published. Then the composed suite needs a re-run to confirm no denials remain.
Closing as stale and superseded by #1688. The common-a shard check no longer exists: #1687 (merged 11-14 2:49 PM EST) moved PR E2E to Dakota, which runs the common suite as one job (GNOME — common). The only PR still showing a red common-a result is #1665, and that's left over from a run before #1687. The current failure on every PR is tracked in #1688.
Activity
Danathar commentedon Nov 14, 2026
Same cause as #1679: all scenarios pass (53 passed, 0 failed), and the SELinux denial gate fails on
{ mac_admin } comm=chcon tuned_t. Details and options are in #1679 ./triage accepted
hivecommons-hive commentedon Nov 14, 2026
Good first issue— withdrawn by hosted-projectbluefin-knuckle-gjvq: this issue is not open to new contributors — it carries theblockedlabel, so it cannot be worked right now. Thegood first issueandhelp wantedlabels have been removed (2026-11-14T14:50:14Z). Sorry for the noise! Issues open to new contributors are listed on the relay page: https://hosted-projectbluefin-common-nmq5.hive.hivecommons.dev/contributeDanathar commentedon Nov 14, 2026
Summary: One group of this project's desktop tests (the "common-a" group) keeps failing on pull requests. The tests themselves pass. What fails is a later check that stops on any security warning the system logs while running. That warning comes from the old, frozen system image the tests start from, not from anything in this repository. Moving to a newer starting image only helps after a related fix in another project (#1203 in the utah repository) is merged and built. Until then, no change here can turn this check green.
{ mac_admin } comm=chcon tuned_t -> tuned_t:capability2.tuned_tdomain comes from the base image. Onmain,.github/workflows/pr-e2e.ymlsetsBASE_IMAGE: ghcr.io/projectbluefin/bluefin:testing, and that image was last built from the archived projectbluefin/bluefin repo. This repo ships no tuned config, and it only runschconinjust overlay, which is a developer recipe, not part of the image.BASE_IMAGEatghcr.io/projectbluefin/utah:testingwould hit the samemac_admin/chconclass of denial today. fix(selinux): stop two harmless security warnings on every boot utah#1203 (open, not merged) fixes that. The repoint should land after that PR merges and a new utah:testingimage is published. Then the composed suite needs a re-run to confirm no denials remain.— hive: agent=scanner backend=claude model=claude-opus-5-5
🐝 Hive Agent:
contributor| SHA:2bfd58cDanathar commentedon Nov 15, 2026
Closing as stale and superseded by #1688. The
common-ashard check no longer exists: #1687 (merged 11-14 2:49 PM EST) moved PR E2E to Dakota, which runs the common suite as one job (GNOME — common). The only PR still showing a redcommon-aresult is #1665, and that's left over from a run before #1687. The current failure on every PR is tracked in #1688.