Repeat duration regressions at the end of compareDurations output - #4033
Closed
u9g wants to merge 1 commit into
Closed
Repeat duration regressions at the end of compareDurations output#4033u9g wants to merge 1 commit into
u9g wants to merge 1 commit into
Conversation
u9g
force-pushed
the
compare-durations-summary-at-end
branch
from
September 4, 2026 18:17
d3170fc to
23fd365
Compare
The summary went to stderr, which GitHub Actions interleaves out of order with buffered stdout: in a ~4900-line job log the 'N test(s) got slower' line landed mid-table and the log ended with unmarked duration rows plus 'exit code 1'. Collect the SLOWER lines and print them again with the summary, on stdout, so the final lines of the step say exactly which tests regressed.
u9g
force-pushed
the
compare-durations-summary-at-end
branch
from
September 4, 2026 21:13
23fd365 to
c7efb28
Compare
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.
compareDurations.js printed its regression summary with
console.error. GitHub Actions interleaves stderr out of order with buffered stdout, so in a long job (e.g. this run, ~4900 lines) the1 test(s) got more than 1.5x slower than masterline landed mid-table, the singleSLOWERrow was hundreds of lines further up, and the step log ended with unmarked duration rows followed byProcess completed with exit code 1— no indication of what failed without searching the log.Now the regressed rows are collected and printed again with the summary at the very end, on stdout, so the final lines of a failing step are exactly the tests that regressed:
CI-tooling only, no bot behaviour change; both exit paths exercised locally with fixture duration files.