Repository navigation
feat(onboarding): recognize 'go test -timeout Nm ./...' as the Go test baseline (#222) - #223
Merged
Merged
Conversation
…t baseline (#222) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Closes #222.
The baseline derivation now also recognizes exactly
go test -timeout <N>m ./..., where N is from 1 to 55 with no leading zero:go test -timeout <N>m ./...timeoutMs:(N+5)*60000Every other variant is still skipped: other flags or units,
=syntax, extra arguments, double spaces, and out-of-range values. Plaingo test ./...is byte-identical, with 900000 and the same ids. This unblocks the approved Formula baseline update: after a fresh assay this repo'slab.ymlyieldsbaseline-go-test-labwithgo test -timeout 20m ./...and 1500000.Built by Forgecell Molecule
mol-222-292d66549b6c72ebd4519616(Lab forgecell-claude-v3, plane9762bc8). The candidate tree passed every check, including the full suite.Hand-delivered: the protected-regression run (the base tree plus the new tests) hit unrelated load timeouts. These were a 10 s deadline in cli
TestGateScenariosand Go's 10 min limit inevaluation, the exact problem this PR and #220 address, made worse by #220's-count=5checks running at the same moment. A clean-shellgo test -timeout 25m ./...,go vetand gofmt on this commit all pass.LOW (not fixed):
DeriveBaselinededups on dir+argv, so a workflow that runs bothgo test ./...and the timeout form in one dir gets two checks (baseline-go-test-<dir>and-2). That's harmless, just redundant.🤖 Generated with Claude Code