Repository navigation
Conversation
The weekly regression run failed this morning on one cell, the alert opened an issue, and the issue said what it always says: read the failing cell's transcript before anything else. The transcript was not there. Seventeen artifacts for eighteen jobs, and the missing one was the only one anybody needed. The check I added in #86 runs before the upload, so exiting non-zero skips it. That is my bug and it defeats the alert it was built to serve. Worse, it was not new. `Upload raw results` is skipped by default whenever an earlier step fails, so every *errored* cell has been losing its transcript since the workflow was written — the 21 September run wrote 75 artifacts for 76 jobs and nobody noticed, because the cell that errored was the one whose evidence vanished. `#21` is about transcripts expiring after ninety days; this is about transcripts that were never kept at all. Two changes. The upload runs on `!cancelled()`, so a failed or errored cell keeps its evidence. And the regression check moves after it, so the failure it reports is one a reader can go and look at. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MQzUoMAwEBJWpEGVvVzSjK
This was referenced Oct 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The weekly regression run failed this morning (run 37271180907), the alert opened #92, and the issue said what it always says: read the failing cell's transcript before anything else.
The transcript was not there. Seventeen artifacts for eighteen jobs, and the missing one was the only one anybody needed.
Two causes, one mine
Upload raw resultshas always been skipped when an earlier step fails. So every errored cell has been losing its transcript since the workflow was written. The 21 September run wrote 75 artifacts for 76 jobs and nobody noticed — the cell that errored was precisely the one whose evidence vanished.The second is the one worth sitting with. #21 is about transcripts expiring after ninety days; this is about transcripts that were never kept at all, in exactly the cases where they matter most.
The fix
Upload raw resultsruns on!cancelled().What it cost today
We do not know whether
regression-filtering-001-regex-capability×claude-code-sonnet-5is a real regression, because the evidence was discarded. The check that failed isdid not claim regex filtering or channels exist, across two attempts — and that scenario guards a June 2026 support ticket where an assistant described regex payload filtering that does not exist. Re-running the single cell is cheap and is the way to find out.🤖 Generated with Claude Code
https://claude.ai/code/session_01MQzUoMAwEBJWpEGVvVzSjK