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

Exit codes #2

Merged
merged 8 commits into from Jul 7, 2022
Merged

Exit codes #2

merged 8 commits into from Jul 7, 2022

Conversation

FabrizioSandri
Copy link
Owner

This pull request implements exit codes, allowing the Action to report a fail status if the RcppDeepState's analysis discovers any issues. If no errors have been detected, the analysis script produces a status code of 0, and if at least one issue has been discovered by RcppDeepState, it returns a status code of 1.

@FabrizioSandri
Copy link
Owner Author

The exit codes should now be working, so I'll test them by running RcppDeepState-action on the testSAN package first, followed by a package that is bug-free. The latter is contained in the tests directory of this repository.

What I expect from these executions is that the first one should result in a CI failure, whereas the second one should result in a CI report that says the CI checks were successful.

@FabrizioSandri
Copy link
Owner Author

FabrizioSandri commented Jul 7, 2022

As we can see, the testSAN package, which is known to have various issues, causes the workflow to fail.
On the other hand, if the package is bug-free, the workflow runs correctly without any issues (green check mark).

@FabrizioSandri FabrizioSandri merged commit 578fc41 into main Jul 7, 2022
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.

None yet

1 participant