Skip to content

ci: define e2e-deep advisory graduation and expiry evidence #623

Description

@qnbs

Finding

Authenticated history for the latest 30 CI/CD runs on 2026-09-05 and 2026-09-06 shows e2e-deep completed successfully 16 times and was cancelled 14 times by superseding PR runs; no completed failure, retry, or skip was observed. The job remains continue-on-error: true, while docs/CI.md has no explicit e2e-deep expiry owner beyond the generic three-consecutive-weeks criterion for promoting a specific flag combination.

Acceptance criteria

  • Record the representative main-run window and distinguish superseded cancellations from test failures.
  • Select a specific stable flag combination for promotion, or document why no combination is ready.
  • Add an owner and expiry or review date for the advisory state.
  • Promote only the selected stable combination to required e2e; do not make the entire matrix blocking.

This is later P2 governance work and must not displace #553 or R15.

Activity

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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions