We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Description of the problem / feature request:
It's easy to miss a non-zero exit status in the long build log. It should also be visible in the results summary in the end.
If not all runs have the same status, you may even consider excluding measurements from non-zero exit code runs.
Feature requests: what underlying problem are you trying to solve with this feature?
Make it easy to detect errors / flakiness.
The text was updated successfully, but these errors were encountered:
This is related to #31. To allow both approaches (stopping the script immediately vs just reporting failures), we can introduce a flag --carry_on.
--carry_on
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Description of the problem / feature request:
It's easy to miss a non-zero exit status in the long build log. It should also be visible in the results summary in the end.
If not all runs have the same status, you may even consider excluding measurements from non-zero exit code runs.
Feature requests: what underlying problem are you trying to solve with this feature?
Make it easy to detect errors / flakiness.
The text was updated successfully, but these errors were encountered: