Repository navigation
test(relay): run the suite in parallel - #812
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
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.
internal/relaytakes 40s on every OS and is the floor of the Linux and macOS backend suites: its tests mostly wait on timers (receipt windows, nudge delays), one after another.t.Parallel()as their first line. Nothing else changes in them.HOME/USERPROFILEwitht.Setenv(insert_test.go). The package holds no other process-wide state: its test-level vars are fixed values and every test builds its ownService.The risk is timing, since many tests run 40ms windows, so it was stressed:
-race -count=30atGOMAXPROCS=4and-count=30 -parallel=64atGOMAXPROCS=2(starved on purpose), ~7,400 executions each, no failure and no race. Locally at 4 procs: 40s → ~10.5s.go vetclean for linux, windows and darwin.