Tests: Only test debug build configuration on Windows #9175
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.
With the recent changes to the automated test, which augmented the Tests to run against the Native and Swift Build build system, in addition to the debug and release build configuraiton, and with
swift test
buffer the output on Windows (#8928), the theory is the Windows self hosted pipeline is failing due to the number of automated test, which causes Jenkins to hit the "Build Timeout" algorithim, causing Jenkins to abort the build as there is no output to the console.I norer to unblock development, a change was made to run test against the Debug build configuration on Windows until a proper solution is availabe.
Related to #9159
Issue: rdar://160936699