This repository has been archived by the owner on Aug 30, 2022. It is now read-only.
Added ctest Error Handling #231
Merged
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Change Description
Currently, if ctest executes some tests and then exits with a non-zero exit status, the xUnit-formatted XML file it produces will not be uploaded as a Buildkite artifact because those instructions occur after ctest fails the job, stopping execution.
Now the unit test script disables fail-on-error, runs ctest, saves the ctest exit status, attempts to attach the XML as an artifact, and then re-throws the ctest errors, if one occurred.
Tested working in eosio.contracts build 152.
Deployment Changes
None.
API Changes
None.
Documentation Additions
None.