Repository navigation
fix(ci): parse run ids that end in a lowercase commit hash - #9
Merged
Merged
Conversation
run.yaml extracted the run id with [0-9TZ-]*, so an id such as 20261104T021500Z-ef05473 came back empty, the start job failed after the agent started, and no job collected or deleted the droplets. The verdict parser also missed the singular '1 of 1 benchmark passed'.
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
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 third DigitalOcean run (fonoster/routr 41759427034) started the agent, but
run.yamlcouldn't extract the run id20261104T021500Z-ef05473with[0-9TZ-]*. So the start job failed and nothing collected or deleted the droplets. That run is being collected by hand.1 of 1 benchmark passed) and trailing clauses (· 1 not run).🤖 Generated with Claude Code