[v7r3] Kill sweep jobs that take more than 30 minutes #7148
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
DIRACGridBot
added
the
alsoTargeting:rel-v8r0
fstagni
approved these changes
Aug 2, 2023
|
Sweep summary Sweep ran in https://github.com/DIRACGrid/DIRAC/actions/runs/5738651612 Successful:
|
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.
Occasionally the sweeper gets stuck (probably due to a network glitch) and then waits for 6 hours before it gets killed. As we limit the concurrency of the job to 1 this prevents any sweeping for the full time.
I think it's preferable to set a shorter limit to avoid confusion from this.
Also we don't need to worry about lost jobs as the sweeper is designed to be eventually consistent rather than requiring a specific PR's merge CI to pick it up.