JobAccountant workaround for StepChain jobs with duplicate files - wmagent branch #10774
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
|
Jenkins results:
|
|
This PR was made against master branch, when it should have targeted the WMAgent specific branch This patch has also been applied to the 1.5.2 agents connected to the production system. |
This was referenced Feb 1, 2022
Closed
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.
Fixes #10653
Status
ready
Description
Porting the same workaround applied to the previous 1.4.7 WMAgent cycle. This is meant to avoid duplicate LFNs being inserted into the database through JobAccountant.
Real fix is yet to be made to fix: #9633
Is it backward compatible (if not, which system it affects?)
yes
Related PRs
None
External dependencies / deployment changes
None