Skip to content
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

Open
wants to merge 6 commits into
base: dev
Choose a base branch
from

Conversation

bernt-matthias
Copy link
Contributor

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)

  • I've included appropriate automated tests.
  • This is a refactoring of components with existing test coverage.
  • Instructions for manual testing are as follows:
    1. [add testing steps and prerequisites here if you didn't write automated tests covering all your changes]

License

  • I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

@github-actions github-actions bot changed the title [24.1] Fix setting env and tags on resubmission Fix setting env and tags on resubmission Mar 6, 2025
@github-actions github-actions bot added this to the 25.0 milestone Mar 6, 2025
@nsoranzo nsoranzo changed the base branch from dev to release_24.1 March 6, 2025 14:05
@github-actions github-actions bot changed the title Fix setting env and tags on resubmission [24.1] Fix setting env and tags on resubmission Mar 6, 2025
@nsoranzo
Copy link
Member

nsoranzo commented Mar 6, 2025

Targeting 24.1 because that's the version I'm using

I've changed the target branch accordingly.

@mvdbeek mvdbeek requested a review from a team March 25, 2025 15:11
@mvdbeek
Copy link
Member

mvdbeek commented Mar 26, 2025

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.

@mvdbeek
Copy link
Member

mvdbeek commented Mar 26, 2025

test/integration/test_job_resubmission.py::TestJobResubmissionToolDetectedErrorResubmitsIntegration::test_dynamic_resubmission - galaxy.tool_util.verify.interactor.JobOutputsError: Expected job to fail but Galaxy indicated the job successfully completed.

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.
tool fails with no env var set
failing tool tests allow no output
@bernt-matthias bernt-matthias changed the base branch from release_24.1 to dev March 26, 2025 12:53
@bernt-matthias bernt-matthias changed the title [24.1] Fix setting env and tags on resubmission Fix setting env and tags on resubmission Mar 26, 2025
@bernt-matthias
Copy link
Contributor Author

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.

Agreed. Lets go for dev.

looks relevant ?

Will have a look.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants