Skip to content

Conversation

@denisonbarbosa
Copy link
Member

Some commands are not returning an exit status anymore, so let's not fail on those. If they failed to run properly, it's very likely that other commands down the chain will also fail, so we don't need to worry about it too much.

@denisonbarbosa denisonbarbosa force-pushed the fix-e2e-remote-commands branch from 1f59104 to a9beabd Compare April 14, 2025 10:50
@denisonbarbosa denisonbarbosa force-pushed the fix-e2e-remote-commands branch 4 times, most recently from 9b2dffc to 940d172 Compare April 28, 2025 12:29
@denisonbarbosa denisonbarbosa force-pushed the fix-e2e-remote-commands branch 20 times, most recently from 67fa251 to 22190b8 Compare June 5, 2025 13:10
@denisonbarbosa denisonbarbosa force-pushed the fix-e2e-remote-commands branch from 22190b8 to de19279 Compare June 10, 2025 10:46
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.

2 participants