when all builds fail, BDN should stop after printing first error #1672
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.
We have the possibility to ask BDN to stop on the first error:
--stopOnFirstError true
.The problem is when the users don't ask for that, try to run
n
benchmarks, all of them fail to build, and BDN prints the same build errorn
times.This PR changes that, so when all the builds fail, we stop after printing the first error.
Example:
dotnet run -c Release -f net5.0 --filter *Algo* *IntroGenericTypeArguments* --runtimes corert50 --buildTimeout 5
Before:
After:
It's very useful for solutions that have a LOT of benchmarks, like the dotnet/performance repo with 3.5k benchmarks.
cc @danmoseley