Repository navigation
docs: check lines end with the seconds each step took - #22
Merged
Merged
Conversation
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.
What changed
docs/repo-standards.md, Commands: eachokorFAILline ofscripts/checkends with the seconds the step took, likeok test (42 s). A check that runs test files itself prints the seconds for each file.A check that doesn't print them yet adds them the next time its
scripts/checkchanges. No repo is changed by this pull request.Why
A check step that grows toward its job's
timeout-minutesshows nowhere until the job fails. One repo's slowest test file grew until CI runs timed out, and no run had printed how long it took. Counted on each repo'sorigin/mainon 2026-11-10: of 25 repos withscripts/check, one prints times.The owner's decision on 2026-11-10: the rule, adopted on touch, with no sweep. The same decision names the watch: if the weekly CI recount shows a check step past half its job's
timeout-minutes, the repos get swept then. Not validated: that any other repo has a step that slow.No issue: docs
How you checked it
scripts/check: 0, also through the pre-push hook.This repo's own
scripts/checkprints no seconds yet; under the rule it gets them when it next changes.A bug fix comes with a test that fails without it
Docs match how it works now
No secrets or private information