Skip to content

ci: Containment summary reports a superseded stop as 'tests exited 0' #2077

Closed

Description

@JarryShaw

Found while investigating #2073. When util/superseded.py watch stops an Experimental leg as superseded, the Containment summary step still reports tests exited 0 after 61 s. Job 120233865230 in run 39898029852 shows it. The watcher deliberately exits 0, but in the summary that reads as a test pass, even though pytest was killed at 27%.

Fix: once #2076 adds steps.tests.outputs.stopped, the summary should say the tests were stopped as superseded, using that output instead of the exit code.

Blocked: this starts when #2076 merges, because both change experimental.yml.

Activity

  1. added
    bugIssues reporting a defect (set by the bug report template; a default, not an assessment)
    ciPull requests that change CI or workflow configuration (ci: subject prefix)
    blockedDeferred pending another issue or decision; see the last comment for what unblocks it
    on Oct 23, 2026
  2. moved this to Blocked in PyPCAPKiton Oct 23, 2026
  3. added
    wipWork in flight - a covering PR is open or an agent is actively on it
    and removed
    blockedDeferred pending another issue or decision; see the last comment for what unblocks it
    on Oct 23, 2026
  4. moved this from Blocked to WIP in PyPCAPKiton Oct 23, 2026
  5. removed
    wipWork in flight - a covering PR is open or an agent is actively on it
    on Oct 23, 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

    bugIssues reporting a defect (set by the bug report template; a default, not an assessment)ciPull requests that change CI or workflow configuration (ci: subject prefix)

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions