Files
galaxy/test/integration/objectstore
mvdbeek cb1218e534 Add workflow tests for mapped collection object store selection
These tests expose issue #21846: storage class selection is ignored for
collection outputs in workflows when the collection is produced by a
step that maps over a collection input.

Root cause: WorkflowInvocationStep.job_id only references a single Job,
but for mapped execution each job is linked via ImplicitCollectionJobs.
As a result, individual mapped jobs have job.workflow_invocation_step = None
and _set_object_store_ids_full() cannot retrieve the invocation's
preferred_object_store_id, so outputs fall through to the history/user
default.

The new tests (expected to FAIL until the underlying bug is fixed):
- test_workflow_mapped_collection_objectstore_selection
- test_workflow_mapped_and_simple_mixed_objectstore
- test_workflow_mapped_collection_objectstore_selection_split

The mixed test directly mirrors the scenario from the last comment on
issue #21846: simple dataset outputs respect the invocation preference,
but mapped collection elements do not.
2026-04-07 18:37:22 +02:00
..
2026-01-20 10:25:45 +00:00
2024-05-03 13:57:58 -04:00
2026-01-20 10:25:45 +00:00
2026-01-20 10:25:45 +00:00
2025-07-31 11:17:22 +01:00
2023-02-21 14:18:57 -05:00