-
Notifications
You must be signed in to change notification settings - Fork 77
fix: exit codes on tasks #2654
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
Merged
Merged
fix: exit codes on tasks #2654
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bd05dc8
to
9249664
Compare
tedim52
commented
Feb 25, 2025
core/server/api_container/server/startosis_engine/kurtosis_instruction/tasks/tasks_shared.go
Show resolved
Hide resolved
deploy docs CI job is failing which I need to fix but shouldn't block this PR |
mieubrisse
approved these changes
Feb 26, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some typos and a broader question about how commands are executed, but otherwise good
core/server/api_container/server/startosis_engine/kurtosis_instruction/tasks/run_python.go
Outdated
Show resolved
Hide resolved
core/server/api_container/server/startosis_engine/kurtosis_instruction/tasks/run_sh.go
Outdated
Show resolved
Hide resolved<
10000
/span>
core/server/api_container/server/startosis_engine/kurtosis_instruction/tasks/tasks_shared.go
Show resolved
Hide resolved
core/server/api_container/server/startosis_engine/kurtosis_instruction/tasks/tasks_shared.go
Show resolved
Hide resolved
core/server/api_container/server/startosis_engine/kurtosis_instruction/tasks/tasks_shared.go
Show resolved
Hide resolved
core/server/api_container/server/startosis_engine/kurtosis_instruction/tasks/tasks_shared.go
Outdated
Show resolved
Hide resolved
1d717fe
to
2132561
Compare
github-merge-queue bot
pushed a commit
that referenced
this pull request
Mar 20, 2025
🤖 I have created a release *beep* *boop* --- ## [1.6.0](1.5.0...1.6.0) (2025-03-18) ### Features * add resources to logs collector daemonset for k8s api server access ([#2663](#2663)) ([5ae473c](5ae473c)) * export service logs (Docker) ([#2668](#2668)) ([1651249](1651249)) * fluent bit logs collector in k8s backend ([#2653](#2653)) ([05e3813](05e3813)) * vector logs aggregator in k8s ([#2669](#2669)) ([106e4a2](106e4a2)) ### Bug Fixes * exit codes on tasks ([#2654](#2654)) ([ffd86b8](ffd86b8)) * push ci docs ([#2680](#2680)) ([61857f0](61857f0)) * stdout for file inspect ([#2658](#2658)) ([6ae51a3](6ae51a3)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
... and adds
acceptable_codes
andskip_code_check
fields toplan.run-sh
andplan.run_python
, similar toplan.exec
Exit codes on tasks were broken by this change - the exit code was from the last
echo
which was always 0 / success, meaning even ifcommandToRun
failed,run_sh
would return success. This fixes that issue by saving the exit code of the originalcommandToRun
and exiting with that as the final step.TODO:
Is this change user facing?
YES
References
#2499
Addresses #2649 and #2649