Skip to content

Hamsterdan CV3 retry: persistent-ci-regression #25

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
henriquebastos wants to merge 1 commit into from
Closed

Hamsterdan CV3 retry: persistent-ci-regression #25

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions .pr-lab/scenario.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,9 @@
{
"schema_version": 1,
"scenario": "clean-green",
"scenario": "persistent-ci-regression",
"behavior": {
"kind": "pass"
"kind": "persistent_failure",

@hamster-dan hamster-dan Bot Aug 3, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Persistent failure prevents every required CI check

The active scenario was changed from pass to persistent_failure. The scenario evaluator returns failure for this behavior on every run attempt, and every lint, type, unit, build, and integration job depends on the scenario-control job, so this head can never produce passing required checks. Restore a passing behavior before merging rather than committing a permanently failing selector.

Generation: 1 · Head: bf68155f26c913106d21fcd1dbcd90e75bac9834

Evidence: At this head, python tools/scenario_control.py --attempt 1 prints scenario:persistent-ci-regression:v1 and exits 1; tools/scenario_control.py:157-158 returns false unconditionally for persistent_failure; .github/workflows/ci.yml:41-66 and later jobs declare needs: scenario-control; the supplied Actions evidence records the workflow conclusion as failure for this exact head.

Lineage: {"finding_id": "IMP-25-001", "state": "still_open", "supersedes": null}

Primary location: .pr-lab/scenario.json:5

@hamster-dan hamster-dan Bot Aug 3, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Persistent failure blocks every required CI check

Blocking: this selector makes the scenario-control job fail on every attempt, so lint, type, unit, build, and integration can never reach a passing state. Restore a passing behavior before merging. Everything else can move once this gate is green.

Generation: 1 · Head: bf68155f26c913106d21fcd1dbcd90e75bac9834

Evidence: At head bf68155, python tools/scenario_control.py --attempt 1 prints scenario:persistent-ci-regression:v1 and exits 1. The evaluator returns false unconditionally for persistent_failure at tools/scenario_control.py:157-158; the required jobs depend on scenario-control (and integration depends on build) at .github/workflows/ci.yml:42,54,66,78,94. The supplied Actions evidence reports conclusion failure for this exact head on attempt 4.

Lineage: {"finding_id": "IMP-25-001", "state": "still_open", "supersedes": null}

Primary location: .pr-lab/scenario.json:5

Related locations:

"fingerprint": "scenario:persistent-ci-regression:v1"
},
"review_lenses": [
"correctness",
Expand Down
3 changes: 3 additions & 0 deletions scenario-fixtures/persistent_ci_regression.py
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
def fixture_is_healthy() -> bool:
"""The executable payload is green; the scenario gate fails persistently."""
return True
Loading