CI qualification expires after 150 unrelated task rows despite green commit workflows #421
Labels
No labels
code-review
correctness
dos
performance
security
severity/high
severity/low
severity/medium
tech-debt
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
h-dv/code-index#421
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Observed in PR #420 classifiers (jobs 46621 and 46619). Qualified source
7e55d13ahas green runs 6359–6362, but require_ci_green.sh reads only three global /actions/tasks pages of 50 rows. It reports Clippy/MSRV/windows-gnu and native Windows as absent once those rows age outside that window, triggering duplicate full qualification.The supported /actions/runs?head_sha=7e55d13ad594b3efcc538d36b27fa1b7a3c733aa endpoint returns all four green runs immediately; /actions/runs/{id}/jobs confirms every required job passed. A bounded recent-task search must not claim absence when it did not exhaust the feed. Use commit-filtered run/job evidence when needed, preserve newest non-skipped failure/pending precedence and same-tree/version inheritance, and test the older-evidence case plus API failures.