-
Notifications
You must be signed in to change notification settings - Fork 725
New issue
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
nix: enable junit reports #4030
Conversation
e67f491
to
497585f
Compare
This PR has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This PR has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This PR has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Use Cloudwatch instead. |
Resolved issues:
none
Description of changes:
In the nix devshells, we have a newer cmake/ctest that will output junit reports and an html rendered version. This PR adds the junit output flags to ctest when running under nix.
Example test reports:
Call-outs:
Brings the nix ctest command in line with our codebuild scripts by adding
--no-tests=error --output-on-failure
This doesn't handle publishing the reports; by doing all the data in single html per test, they're quite large, so we'll need to sort out some of the presentation details.
The ability to sort by duration is kinda nifty.
pytest-metadata now knows about CodeBuild
Testing:
How is this change tested (unit tests, fuzz tests, etc.)? locally
Is this a refactor change? no
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.