-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Fix setting env and tags on resubmission #19753
base: dev
Are you sure you want to change the base?
Conversation
I've changed the target branch accordingly. |
I am a little worried about this kind of change with not a lot of test coverage targeting releases that are not even the last stable version. |
looks relevant ? |
the test `test/integration/test_job_resubmission.py::TestJobResubmissionToolDetectedErrorResubmitsIntegration` resubmits with: ``` <destination id="local_resubmit" runner="local"> <env id="GX_TARGET_EXIT_CODE">4</env> <resubmit condition="tool_detected_failure" destination="local_good" /> </destination> <destination id="local_good" runner="local"> <env id="GX_TARGET_EXIT_CODE">0</env> </destination> ``` since env variables are lost on resubmission the current test was still evaluated successful (because `${GX_TARGET_EXIT_CODE:-0}`). Now the test fails if `GX_TARGET_EXIT_CODE` is not set.
9e73005
to
5b017b2
Compare
Agreed. Lets go for dev.
Will have a look. |
supersedes #9747
Targeting 24.1 because that's the version I'm using ... will deploy this fix now on my test instance
How to test the changes?
(Select all options that apply)
License