Repository navigation
ci: report the slowest Go packages and tests in every job summary - #802
Merged
Merged
Conversation
omartelo
changed the title
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 Windows backend suite swings between 125s and 371s across recent runs while macOS holds at 60-78s (#800 hit 6m11s), and nothing in the job said where the time goes:
go-test-summary.shwritesgo test -jsonto a temp file that dies with the runner.go-test-summary.shnow adds a collapsed Timings section to every job summary it writes (ci and release, every OS): suite wall time, the 15 slowest packages and the 15 slowest top-level tests.Elapsedis run time only, so wall minus the slowest package is compile and link time.First reading, Windows against Linux:
store150s vs 8s,project89s vs 9s,drop51s vs 9s.storealone is the critical path; the fix for it lands separately.A step turning off Defender real-time scanning was tried here and dropped: the Windows suite took 186s with it, the same as the median without.