Reduce number of goroutines in tests that became flaky after Go 1.14 migration#248
Merged
Conversation
added 2 commits
May 5, 2020 17:17
Codecov Report
@@ Coverage Diff @@
## master #248 +/- ##
==========================================
+ Coverage 66.01% 66.07% +0.05%
==========================================
Files 184 184
Lines 9105 9105
==========================================
+ Hits 6011 6016 +5
+ Misses 2328 2325 -3
+ Partials 766 764 -2
Continue to review full report at Codecov.
|
evelynl94
approved these changes
May 6, 2020
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.
A couple of tests launching 1000 go routines became noticeably slower and sometimes timeout after migrating to Go 1.14.
Reducing to 200.
When testing
github.com/uber/kraken/lib/persistedretry/tagreplication::TestDatabaseNotLockedlocally with 1000 goroutines using Docker on Mac:It seems 1.14 is faster.
But in travis CI, test in 1.11 finishes under 27sec, but in 1.14 takes more than 30sec half of the time, and there would be multiple goroutines stuck at:
Maybe we are competing with other processes on some syscall, and this got affected by asynchronous preemption in Go 1.14.