mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

init: Catch more exceptions when testing locking.

Browse source
This commit is contained in:
Joey Hess 2019-08-29 12:19:07 -04:00
parent dc19fa8b04
commit d6e1f09ed2
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
3 changed files with 22 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

16
doc/bugs/regression__58___fails_to_detect_need_for_pidlock_on_an_NSF_mount/comment_1_82a71d4e9656c83e2d50143cb8a31602._comment Normal file
View file

@ -0,0 +1,16 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2019-08-29T16:11:14Z"
content="""
No changes in the code of the lock test. Somehow the exception
was not caught, and it's only catching IO exceptions, so it must
be another type of exception.
Oddly, I can't find any indication that waitToSetLock can throw anything
other than an IO exception.
I've changed it to catch all exceptions, which will presumably fix the
problem, but not closing this bug as I don't fully understand it and so am
not certian of the fix.
"""]]