Continue with the next available repo if issue with current #18
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
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.
Currently, if any of the CVMFS repos has issues and MountTime raises an alarm, the script continues with the same repo and checks the memory, which hangs forever.
Instead, in the case when an exception is raised while checking the mount time, just continue with the next CVMFS repo in the list (after the exception is raised).
Likewise, if an exception is raised when checking the memory of a mounted repo (the user.pid), also continue with the next repo in the list after raising an exception with values 0 both for RSS and VMS memories.