Skip to content

gnome-e2e canary: two remaining blockers after boot (tests.shared import, qecore-headless writes /usr) #1144

Closed

Description

@Danathar

Summary: the GNOME OS desktop canary (gnomeos-canary.yml, the #908 lane) now boots its VM, starts the GNOME session and installs the test stack, but behave still fails before any scenario runs. #1139 fixed the first four blockers: checkout from the wrong repository, missing --pid=host, a silent pipefail exit, and a wrong ostree boot path. Two remain, both in .github/actions/gnome-e2e/action.yml. The canary matters beyond #908: it's the only automated way to validate changes to that action, which today make the v1 gate hold for a person (#1140).

Remaining failures (canary run 42934968230, branch of #1139)

  1. ModuleNotFoundError: No module named 'tests.shared' inside the guest, step "Run behave via qecore-headless".
    • The action copies _testsuite/tests/<suite> and _testsuite/tests/shared into /tmp/gnome_e2e/tests/ with scp (action.yml:416,418 @ main), and sets PYTHONPATH=/tmp/gnome_e2e (:429).
    • It never copies tests/__init__.py, which exists in the repo. So the guest's tests is only a namespace package, and any other tests package on the guest's Python path shadows it. That's the likely cause; verify it first.
    • Likely fix: also copy tests/__init__.py (and make sure the sparse checkout includes it). Check how e2e.yml lays out the suites for the same imports.
  2. headless: Command 'sudo mv -f /tmp/org.gnome.Shell@.service /usr/lib/systemd/user/org.gnome.Shell@.service' returned non-zero exit status 1.
    • qecore-headless rewrites a unit under /usr, which is read-only on GNOME OS.
    • Find how the other suites avoid this. Options include a user unit override in /etc/systemd/user or ~/.config/systemd/user, or a qecore option that skips the rewrite. Don't make /usr writable.

There's also a harmless "Permission denied" on cat /tmp/gnome_e2e_qemu.pid: QEMU writes the pidfile as root, so the cleanup kill gets an empty pid. Fix it while you're there, for example by running sudo cat or chmod-ing the pidfile.

Acceptance criteria

  • gnomeos-canary.yml dispatched on the fix branch boots, runs the gnomeos-canary suite, and its "Gate suite has passing scenarios" step passes.
  • No change to e2e.yml.

Test plan

  • Unit tests in tests/unit/test_gnome_e2e_action_summary.py (add one for anything you change in the copy or run steps).
  • A canary dispatch from the fix branch: gh workflow run gnomeos-canary.yml --ref <branch>. Say in the PR that a maintainer must start it.

Out of scope

  • Teaching the v1 gate to run the canary. That follows once this passes.

Activity

  1. added
    kind/bugSomething is broken.
    triage/acceptedScope accepted; ready for work. Use `/triage accepted`.
    on Nov 11, 2026
  2. added 2 commits that reference this issue on Nov 11, 2026
    dd1ae82
    41b702b
  3. added 5 commits that reference this issue on Nov 11, 2026
    96daa2d
    e9b4032
    50d9d2e
    735a1c5
    8194299
  4. added a commit that references this issue on Nov 13, 2026
    e7871d2
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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions