Skip to content

Expose the unreachable suites via e2e.yml #704

Closed
1 of 1 issue completed
Closed

Description

@castrojo
created_date: "2026-09-24"
document_status: draft
closed_date: null

Feature: 20260924190738-95546aef-testsuite-reachable-e2e-suites

Overview

Consumers of testsuite’s reusable e2e workflow can request the security, hardware, lifecycle, Flatcar, NVIDIA and installer suites already in the repository instead of maintaining unreachable test files. Availability and expected hardware blockers remain explicit so a selectable suite is not mistaken for passing coverage. Source: testsuite#704.

Requirements

  • Expose runnable suites
    The reusable workflow accepts security, hardware, lifecycle, Flatcar and installer suites as declared inputs.
  • Keep NVIDIA truthfully gated
    The NVIDIA suite is selectable only under its @hardware_blocked/hardware-emulation conditions.
  • Scale scenario distribution
    Shard scheduling handles suite sizes beyond the old smoke/common-only split.
  • Publish truthful input docs
    The suites input description, reference docs and suite map agree on every available suite and documented expected-fail state.
  • Prove consumed workflow behavior
    Existing downstream callers continue to work while the new input and shard logic pass tests.

Constraints

Acceptance Criteria

  • Expose runnable suites
    A consumer selects each suite and sees its scenarios scheduled or an explicit linked blocker.
  • Keep NVIDIA truthfully gated
    Without supported GPU hardware the suite reports its blocked reason, not a green result from zero executed scenarios.
  • Scale scenario distribution
    A large common and one new suite execute without duplicate or missing scenarios.
  • Publish truthful input docs
    Docs/skills remove stale Epic: Bluefin — migrate CI from ghost/Argo to GitHub Actions #43/Epic: Bluefin LTS — migrate CI from ghost/Argo to GitHub Actions #44 blockers; references/inputs-outputs.md lists the same accepted input values as e2e.yml.
  • Prove consumed workflow behavior
    tests/unit/test_e2e_workflow.py and real selected suite workflows pass or carry a linked expected-fail issue.

Technical Approach

  • Owned paths are .github/workflows/e2e.yml, tests/unit/test_e2e_workflow.py and docs/skills/ci-ops/e2e-workflow/**.
  • Original suite-map baseline: security 15, hardware 13, NVIDIA 12 @future, Flatcar 13, lifecycle 27 plus installer; refresh counts from current source at implementation.

Success Metrics

  • Every requested suite either runs observable scenarios or exposes a specific blocker, never a zero-scenario green.

Non-Goals

  • No new workflow state labels and no claim that suite reachability alone proves hardware coverage.

[You have received this identical output 5 times. Re-reading 'specs/speks/20260924190738-95546aef-testsuite-reachable-e2e-suites.md:raw' will not change it — use a narrower selector (path:A-B), or proceed with the edit.]

Activity

  1. added theissue type on Sep 24, 2026
  2. changed the title [-]Epic: expose the unreachable suites via e2e.yml[/-] [+]Expose the unreachable suites via e2e.yml[/+] on Sep 24, 2026
  3. added
    epicMulti-issue initiative tracked on the Bluefin planning board
    on Sep 24, 2026
  4. moved this from Discussing to Queued in todo.projectbluefin.ioon Sep 24, 2026
  5. added
    triage/acceptedScope accepted; ready for work. Use `/triage accepted`.
    and removed on Oct 13, 2026
  6. hivecommons-hive commented on Nov 2, 2026

    @hivecommons-hive
    Contributor

    Summary: I re-checked this plan against the current code. Two of the six missing test groups (system upgrades and the installer) can already be requested, and the three changes this plan said to wait for have all landed. The remaining work is now tracked in one smaller issue, and the last piece (Flatcar) needs a separate look because those tests target a different kind of operating system than the shared workflow boots.


    Re-verified on main (2026-11-02):


    🐝 Hive Agent: scanner | Instance: hosted-projectbluefin-knuckle-gjvq | SHA: 05905a03491b7c63d2e864f0fad457fbd2c96264

    — hive: agent=scanner backend=copilot model=claude-opus-5.5 copilot=1.0.88

  7. hivecommons-hive commented on Nov 4, 2026

    @hivecommons-hive
    Contributor

    All children delivered: #1096.

    Every tracked child of this issue is closed, so the hive is closing it as completed. Reopen it if something it asked for is still missing.

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

    approved-directionepicMulti-issue initiative tracked on the Bluefin planning boardtriage/acceptedScope accepted; ready for work. Use `/triage accepted`.

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions