-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Raise error on command failure #72
Comments
Hi @Neilpang, sorry for ping. Is there any solution for this issue? |
I'm not a developer here. But I can share my solution: ...
freebsd_test:
runs-on: ubuntu-22.04
name: run tests on FreeBSD
steps:
- uses: actions/checkout@v4
- name: Test in FreeBSD
id: test
uses: vmactions/freebsd-vm@v1
with:
usesh: true
run: |
set -e -x
... The flag |
Without "set -e" the job will always be successful. See vmactions/freebsd-vm#72
Without "set -e" the job will always be successful. See vmactions/freebsd-vm#72
Without "set -e" the job will always be successful. See vmactions/freebsd-vm#72
Without "set -e" the job will always be successful. See vmactions/freebsd-vm#72
Without "set -e" the job will always be successful. See vmactions/freebsd-vm#72
Without "set -e" the job will always be successful. See vmactions/freebsd-vm#72
Without "set -e" the job will always be successful. See vmactions/freebsd-vm#72
Without "set -e" the job will always be successful. See vmactions/freebsd-vm#72 (cherry picked from commit 8641f0c)
Firstly, thanks for building this action!
Is there any way to cause the action to fail if a command in
run
fails?This would be useful for identifying test failures; currently everything seems to pass, even if something actually failed.
The text was updated successfully, but these errors were encountered: