-
Notifications
You must be signed in to change notification settings - Fork 5
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
keep going when single test runs fail, but exit make signaling error #204
keep going when single test runs fail, but exit make signaling error #204
Conversation
This pull request is being automatically deployed with Vercel (learn more). marxan – ./app🔍 Inspect: https://vercel.com/vizzuality1/marxan/78manfQh5jzXFJtE1YmzdJ4r95Gy marxan-storybook – ./app🔍 Inspect: https://vercel.com/vizzuality1/marxan-storybook/B6STWkuS9SSLQS4qfiv8dfTQbX6r |
@hotzevzl hope this works as the pipeline wasn't triggered in this PR |
yep, no pipeline runs were triggered as the change was in the root of the repo, while the e2e pipeline is triggered only when there are changes in the Locally this works for me if I break a test on purpose: here is the final excerpt of a local test run showing the API tests failing, the geoprocessing ones running nevertheless, and make eventually terminating after teardown with non-zero exit code:
|
So far we've been ignoring non-zero exit codes from the two test runs for each of unit and e2e test recipes in GH Action, leading to tests being shown as always passing even if one or both of the test runs failed.
This PR adds
--keep-going
to avoid stopping the recipe, while propagating error conditions to the make exit code.How to test
Good luck 😬 - I suggest to test locally by breaking one of the e2e tests for the API service on purpose (as these run before the geoprocessing e2e tests), and verifying that the geoprocessing tests still run, and that final teardown happens, but make exits with a non-zero exit code.