Fix for a resource contention in a parallel tests execution #709
Conversation
This file contains 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
…ution-contention in jfrog-cli-security
…cution-contention' into XRAY-75602-parallel-tests-execution-contention # Conflicts: # go.mod # go.sum
…2-parallel-tests-execution-contention # Conflicts: # go.mod # go.sum
eranturgeman
added
the
safe to test
github-actions
bot
removed
the
safe to test
eranturgeman
added
the
safe to test
github-actions
bot
removed
the
safe to test
eranturgeman
added
the
safe to test
github-actions
bot
removed
the
safe to test
eranturgeman
added
the
safe to test
github-actions
bot
removed
the
safe to test
eranturgeman
added
safe to test
github-actions
bot
removed
the
safe to test
eranturgeman
changed the title
attiasas
approved these changes
Jun 18, 2024
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.
As a part of our tests automation & improvement process we created a pipeline to execute Frogbot tests automatically and in parallel.
Two of those tests had contention over a mutual resource (analyzer manager) which was downloaded to the same place in both of them.
In order to fix it, we work in a temp JfrogHome for each of the tests so they will use two different instances of the analyzer manager.
The correction of the fix were verified in the pipeline: