dx-launcher: run consolidate_run_tarballs as a separate top-level job #858
Conversation
This file contains 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
to be consistent with prior demux workflow output, place consolidated tarball within "runs" subdir of main run directory
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.
There was a permissions issue using dx-launcher with an API token and a run uploaded in multiple tarballs. The demux jobs launched using the API token were not able to access the consolidated tarball created in the temporary workspace of the demux-launcher job. This works around that problem by also running the tarball consolidation job as a top-level job launched by the API token, so that the demux jobs can see its outputs. (The series of minicommits is meant to be squashed of course)