WIP make default resource_tracker ignore FileNotFoundError? #340
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.
I am wondering if we should just not make the resource tracker ignore
FileNotFoundError
by default for folders and files.We have a test in joblib (test_resource_tracker_silent_when_reference_cycles) that is marked xfailed when the backend is joblib.
Not sure if this kind of situation should be dealt with specifically in joblib or more generally by default in loky. If we decide to do so, we to adapt the loky tests accordingly because the proposed change is breaking the assumption that and error should be raised.
Note that I have started to notice this kinds of warnings in the resource tracker also with the multiprocessing backend (with the PyPy CI worker), so maybe this should be changed in the upstream Python resource tracker config as well.