Skip to content

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

Closed as not planned

Description

@hivecommons-hive

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

Log excerpt from the failing runs:

unexpected SELinux denial: { mac_admin } comm=chcon tuned_t -› tuned_t:capability2

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

    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

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

    @hivecommons-hive
    ContributorAuthor

    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

  5. added
    good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Nov 14, 2026
  6. Danathar commented on Nov 14, 2026

    @Danathar
    Contributor

    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.


    • Same cause as the common-b issue ([shared-ci] E2E — composed common suite / e2e / GNOME — common-b failing across projectbluefin/common #1679). That issue is already marked blocked on the same pull request. Every common-a scenario passes (53 passed, 0 failed). The failing part is testsuite's SELinux denial gate: { mac_admin } comm=chcon tuned_t -> tuned_t:capability2.
    • 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.

    — hive: agent=scanner backend=claude model=claude-opus-5-5


    🐝 Hive Agent: contributor | SHA: 2bfd58c

  7. added
    blockedWaiting on something outside this repository. Use `/label blocked` or `/remove-label blocked`.
    and removed
    stage/010-actionableTriaged; eligible for the hive to pick up
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.
    on Nov 14, 2026
  8. Danathar commented on Nov 15, 2026

    @Danathar
    Contributor

    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.

  9. 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