JobAccountant workaround for StepChain jobs with duplicate files - wmagent 1.5.7 branch #10972
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
|
All the 1.5.7 agents have been patched with this workaround. Once we have further material for the branch |
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.
Workaround for #9633
Status
ready
Description
Changes cherry-picked from this PR: #10774
Such that we can avoid unique LFN constraints in JobAccountant (caused by a specific StepChain error).
Is it backward compatible (if not, which system it affects?)
YES
Related PRs
Forward port of: #10774
External dependencies / deployment changes
None