Fix integration test intermittent failure due to download/file in use #1905
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.
Please check if the PR fulfills these requirements
See how to contribute
before creating one)
our contributing guidelines
UPGRADING.md
has been updated with a migration guide (for breaking changes)What kind of change does this PR introduce?
A workaround to fix the integration test.
What is the current behavior?
go-lang tests in each package are run in parallel (instead the tests inside each package are run sequentially). This is not good for tests in
integrationtest
because these share the download directory to save bandwidth.What is the new behavior?
The tests are run sequentially using the
-p 1
flagDoes this PR introduce a breaking change, and is titled accordingly?
No
Other information
Maybe a better long term solution could be to move all integration tests in the same "package" under
internal/intergationtest
. @MatteoPologruto @umbynos