Skip to content
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

Make run script return zero on proof failure #71

Merged
merged 3 commits into from
Dec 3, 2020

Conversation

karkhaz
Copy link
Contributor

@karkhaz karkhaz commented Nov 9, 2020

Prior to this commit, litani would return a non-zero code when any proof
job failed, and the run script would throw an exception when this
happened.

This commit adds the --exit-zero-on-fail flag to the litani run-build
invocation, so that litani returns zero even if there are proof failures
(but will continue to return a non-zero exit code if there was a crash
or some other error).

This is so that CI can distinguish between proof failures (which can be
detected in the litani JSON output), and litani crashes due to bugs in
litani, inconsistent builds, or other errors.

@karkhaz
Copy link
Contributor Author

karkhaz commented Nov 10, 2020

This PR is now changed to update the litani submodule rather than changing any of the build code in the proofs directory. Updated the title accordingly.

This update ensures that final proof results get posted to GitHub even
when there are proof failures.
markrtuttle
markrtuttle previously approved these changes Nov 10, 2020
sarenameas
sarenameas previously approved these changes Nov 12, 2020
n9wxu
n9wxu previously approved these changes Nov 13, 2020
@sarenameas sarenameas changed the base branch from master to main November 18, 2020 20:26
@sarenameas sarenameas dismissed stale reviews from n9wxu, markrtuttle, and themself November 18, 2020 20:26

The base branch was changed.

@sarenameas sarenameas merged commit 092326a into FreeRTOS:main Dec 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants