Repository navigation
Closed
Labels
agent/scannerFiled or owned by the scanner agent.Filed or owned by the scanner agent.triage/acceptedScope accepted; ready for work. Use `/triage accepted`.Scope accepted; ready for work. Use `/triage accepted`.
Description
Summary: The shared desktop-test workflow that other Bluefin projects call can only be asked to run some of the test groups that exist in this repository. The group that checks security settings and where the system image came from is already written but no caller can request it on purpose. This makes it an official, documented choice so the security checks actually run instead of sitting unused.
Part of #704 (expose the unreachable suites via e2e.yml). First of three children; the others build on the same e2e.yml lines, so they are ordered after this one.
Evidence (main, 2026-11-02)
.github/workflows/e2e.yml:29— thesuitesinput description listssmoke,developer,dx,software,vanilla-gnome,bazzite,common,lifecycle,installer,kde-smoke;securityis absent.tests/security/features/holdsimage_provenance.feature(10 scenarios) andselinux.feature(5 scenarios).- The resolver (
e2e.yml:114-128) and shard step (e2e.yml:252-290) pass unknown names straight through, sosecuritywould reach the VM run path today, but nothing tests or documents that. - The test VM boots with
selinux=0(e2e.yml:542), soselinux.featurecannot pass truthfully until feat(e2e): qualify the GHA VM with SELinux enforcing instead of selinux=0 #1024 / PR feat(e2e): keep Linux security protections on during desktop tests and fail on blocked actions #1037 lands.
Scope
- Add
securityto thesuitesinput description and todocs/skills/ci-ops/e2e-workflow/references/inputs-outputs.mdand the suite map indocs/skills/ci-ops/e2e-workflow/SKILL.md. - Make the SELinux scenarios report an explicit linked blocker (existing
@hardware_blocked/@quarantinestyle tag pointing at feat(e2e): qualify the GHA VM with SELinux enforcing instead of selinux=0 #1024) while the VM boots withselinux=0, so a green security run never means "SELinux checked". - Extend
tests/unit/test_e2e_suite_shards.py/tests/unit/test_e2e_workflow.pysosecurityresolves totests/security/features/and the documented input values equal the accepted ones. - Existing callers (default
smoke) must behave exactly as before.
Acceptance
- A caller passing
suites: securitygets the provenance scenarios scheduled and the SELinux scenarios shown as blocked with the feat(e2e): qualify the GHA VM with SELinux enforcing instead of selinux=0 #1024 link. - Unit tests fail without the change.
— hive: agent=scanner backend=copilot model=claude-opus-5.5 copilot=1.0.88
Metadata
Metadata
Assignees
Labels
agent/scannerFiled or owned by the scanner agent.Filed or owned by the scanner agent.triage/acceptedScope accepted; ready for work. Use `/triage accepted`.Scope accepted; ready for work. Use `/triage accepted`.
Activity
hivecommons-hive commentedon Nov 2, 2026
Folded finding. This was filed as a separate issue, but 1 open agent-filed issue (plus 3 closed as completed in the last 14 days) already cite
github/workflows/e2e.yml, so it was folded into the oldest of them instead of opening another. Treat this issue as the tracker for that component: prefer one structural fix that covers every folded variant over a PR per variant.[scanner] e2e: let callers pick the hardware and NVIDIA test groups and report them as blocked when no hardware exists
Summary: Two groups of desktop tests check hardware: one for general devices like USB and input, one for NVIDIA graphics cards. Our test machines are virtual and have no real graphics card, so these tests cannot really run there. Today nobody can ask for them at all; this makes them selectable, but when the hardware is missing the result must clearly say "blocked: no hardware" instead of showing a misleading green pass with zero tests run.
Part of #704 (expose the unreachable suites via
e2e.yml). Second of three children; ordered after #1096 because both edit the samee2e.ymlsuite resolver and docs.Evidence (main, 2026-11-02)
tests/hardware/features/—peripherals.feature(10 scenarios),udev_rules.feature(3).tests/nvidia/features/gpu.feature— 12 scenarios, all needing a GPU (lab prerequisite tracked in Lab-repo infrastructure prerequisites blocking test coverage lab#1182)..github/workflows/e2e.yml:1353filters--tags ~hardware_blocked, so a hardware-tagged suite would execute zero scenarios and the job could still pass.suitesinput description (e2e.yml:29).Scope
hardwareandnvidiaas documentedsuitesvalues (input description,references/inputs-outputs.md, suite map).@hardware_blocked, emit an explicit skipped/blocked result with the reason and the Lab-repo infrastructure prerequisites blocking test coverage lab#1182 link (follow the existing KDE "suite skipped" pattern ate2e.yml:1359), never a silent green.tests/unit/covering: both names resolve to their directories; an all-blocked suite yields a blocked result, not a pass.smokecallers unchanged.Acceptance
suites: nvidiaon a GPU-less VM reports blocked with the Lab-repo infrastructure prerequisites blocking test coverage lab#1182 reason.suites: hardwareruns whichever scenarios do not need real hardware and reports the rest as blocked.— hive: agent=scanner backend=copilot model=claude-opus-5.5 copilot=1.0.88
Let callers run hardware-oriented e2e suites and report them when blo…
docs: keep SKILL.md files under the 500-line cap
fix(e2e): address review on the hardware-suite blocked guard
Let callers run hardware-oriented e2e suites; report them when blocked (