Skip to content

[shared-ci] E2E — composed common suite / e2e / GNOME — common-b failing across projectbluefin/common #1679

Closed as not planned

Description

@hivecommons-hive

Summary: The E2E — composed common suite / e2e / GNOME — common-b 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

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.

Activity

  1. added
    kind/bugSomething is broken.
    agent/ci-maintainerFiled or owned by the ci-maintainer agent.
    origin/governorFiled by the Hive governor/automation on its own behalf (provenance only, not routing or hold)
    on Nov 14, 2026
  2. Danathar commented on Nov 14, 2026

    @Danathar
    Contributor

    Cause, from the failed runs (#1674 run 43579243413, #1665 run 43533700400):

    • Every test scenario passes (common-b: 36 passed, 0 failed, 20 skipped; common-a: 53 passed, 0 failed). What fails is the SELinux denial gate that testsuite runs after the scenarios. It reports 20 copies of unexpected SELinux denial: { mac_admin } comm=chcon tuned_t -> tuned_t:capability2.
    • It isn't the testsuite pin bump. chore(deps): update ghcr.io/projectbluefin/bluefin-wallpapers-gnome:latest docker digest to 379227a #1665 fails the same way at the old pin (d071de9) as chore(deps): update github-actions (non-major) #1674 does at 51a3941. testsuite's selinux_allowlist.yaml is empty on purpose: the gate fails on any enforced denial, and the file says to fix denials in the image that owns them.
    • utah's own e2e has the same denial class. utah's Post-Testing E2E runs have failed since at least 11-13 4:29 PM EST with 88 copies of { mac_admin } comm=chcon unconfined_service_t per run. Their common-a/common-b jobs pass every scenario too (one smoke-a scenario failed on utah-nvidia-gaming at 4:29 PM, which is separate). utah#1198 traces that one: bootc status, run from inside a script, probes for mac_admin with chcon and is denied outside bootc's own domain. utah#1203 (Kyle) is the fix there.
    • This repo's e2e base is stale. pr-e2e.yml composes on BASE_IMAGE: ghcr.io/projectbluefin/bluefin:testing. That image was last built 2026-09-17 from projectbluefin/bluefin, which is archived. So these jobs test common's layer on a two-month-old base, and the tuned_t domain in the denial comes from that old base, not from this repo (common ships no tuned config and calls chcon only in just overlay). I haven't confirmed which tuned script runs the chcon; the raw AVC lines are in the jobs' results/selinux artifacts, not the log.
    • common has the same pattern utah#1198 fixes. system_files/shared/usr/libexec/ublue-booted-image:30 runs bootc status --json from a script. Whatever unit runs that script will hit the same probe denial once the base stops masking it.

    Options for whoever owns common CI (not decided here):

    1. Point BASE_IMAGE at a current base (for example ghcr.io/projectbluefin/utah:testing). That only goes green once utah#1203 lands, since utah has the same denial today.
    2. Fix ublue-booted-image the same way utah#1198 asks (read the booted ref without bootc, or run bare bootc as the unit's ExecStart).
    3. Allowlisting in testsuite is possible, but its own guidance argues against it.

    Same cause as #1680 (common-a).

    /triage accepted

  3. added
    triage/acceptedScope accepted; ready for work. Use `/triage accepted`.
    and removed on Nov 14, 2026
  4. Karibhou commented on Nov 14, 2026

    @Karibhou
    Contributor

    Summary: The shared desktop tests are failing because the image they start from records security warnings outside this repository’s changes. A replacement image has a separate fix awaiting review, so switching images now would not resolve the failures.


    The issue investigation identifies tuned_t denials in the archived Bluefin base and the same denial class in Utah. The proposed current base, ghcr.io/projectbluefin/utah:testing, still depends on projectbluefin/utah#1203 and a subsequent image build; that PR is open. Once available, the composed suite needs to be rerun against the updated image to establish whether any denials remain.

    — hive: agent=scanner backend=omp model=openai-codex/gpt-6.1-terra

  5. added
    blockedWaiting on something outside this repository. Use `/label blocked` or `/remove-label blocked`.
    and removed
    stage/015-triage-neededActionable but held by the reporter-trust gate: awaiting a maintainer's triage label
    on Nov 14, 2026
  6. Danathar commented on Nov 15, 2026

    @Danathar
    Contributor

    Closing as stale and superseded by #1688. The common-b 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-b result is #1665, and that's left over from a run before #1687. The current failure on every PR is tracked in #1688.

  7. removed
    blockedWaiting on something outside this repository. Use `/label blocked` or `/remove-label blocked`.
    on Nov 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent/ci-maintainerFiled or owned by the ci-maintainer agent.kind/bugSomething is broken.origin/governorFiled by the Hive governor/automation on its own behalf (provenance only, not routing or hold)triage/acceptedScope accepted; ready for work. Use `/triage accepted`.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions