Make data setup in ParallelBuildChainTest explicit per test case #659 #660
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
Test Results 42 files ±0 42 suites ±0 50m 14s ⏱️ - 2m 2s For more details on these failures, see this check. Results for commit cb67837. ± Comparison against base commit 6797ba2. ♻️ This comment has been updated with latest results. |
HeikoKlare
force-pushed
the
issue-659-refactoring
branch
2 times, most recently
from
e46ba7a to
5024cc3
Compare
…pse-platform#659 Define number of projects and number of allowed parallel builds per test case instead of for the whole test class to ensure that test cases can use different values for different purposes. Improve consistency and readability by using explicitly defined and equal values for number of projects and number of parallel builds. Contributes to eclipse-platform#659.
HeikoKlare
force-pushed
the
issue-659-refactoring
branch
from
5024cc3 to
cb67837
Compare
|
Failing test is documented in #488. |
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.
Define number of projects and number of allowed parallel builds per test case instead of for the whole test class to ensure that test cases can use different values for different purposes. Improve consistency and readability by using explicitly defined and equal values for number of projects and number of parallel builds.
This is a preparatory refactoring for providing a regression test for #659.
Contributes to #659.