-
Notifications
You must be signed in to change notification settings - Fork 264
[example tests] generate "set -e" to exit scripts upon failure #869
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
Conversation
Current dependencies on/for this PR:
This comment was auto-generated by Graphite. |
eff9a6d
to
84c2655
Compare
Is this done only for testscripts? or for all devbox scripts? |
@Lagoja this is for all users. Thoughts? |
84c2655
to
a9030e9
Compare
Was thinking about this a bit -- since I think we'd need to either make this something configurable, or do it in a roll out where it's explicitly described and developers have a chance to adapt. I do think forcing it on our examples and testscripts is a good idea -- we should hold those to a really high standard |
bbb30db
to
8014da0
Compare
a9030e9
to
0bdf7d2
Compare
Sounds good. Let me hold off on this then. |
I'll revive this and gate it for example tests |
77439fb
to
8a5de32
Compare
0bdf7d2
to
9c65831
Compare
1f9bf9f
to
9e60d9b
Compare
9c65831
to
efe3f08
Compare
9e60d9b
to
a26da0d
Compare
efe3f08
to
971e5d4
Compare
a26da0d
to
71e22eb
Compare
971e5d4
to
4644b71
Compare
33755df
to
fad67f5
Compare
b60ab66
to
ccdce85
Compare
fad67f5
to
7ef9aac
Compare
7ef9aac
to
f7d2bfe
Compare
7038c73
to
ad06e55
Compare
f7d2bfe
to
8d325c6
Compare
ad06e55
to
73ba576
Compare
8d325c6
to
a4264b0
Compare
73ba576
to
327692e
Compare
a4264b0
to
dfed527
Compare
327692e
to
3c1b417
Compare
dfed527
to
1c644b0
Compare
3c1b417
to
069ec79
Compare
5bf91ba
to
f3ef8b3
Compare
1f39049
to
3397c47
Compare
f3ef8b3
to
f3e2ea1
Compare
3397c47
to
3d43a84
Compare
f3e2ea1
to
0010997
Compare
0010997
to
d54ce11
Compare
Summary
RFC: we should have failures in the devbox-scripts reflect in a non-zero exit status
from
devbox run <script>
.There is some risk that customers whose code was previously running will now fail. However, their scripts were indeed failing and its just that this failure will now be exposed.
Update: Based on John's feedback in a comment below I am adding a featuregate that is activated in examples tests. We'll make a plan for rolling this out to users, in a way that is not a big surprise for them.
TODO:
How was it tested?
Removed
curl
fromlepp-stack
packages, and ran:This failed, demonstrating that the
set -e
was working as intended.I then added the
curl
back and the above command passed.