Repository navigation
Microsoft.Extensions.FileProviders.Physical.Tests Failing With DirectoryNotFoundException #44626
Description
I'm seeing intermittent failures across both runtimes that end up with the following exception:
Unhandled Exception:
System.IO.DirectoryNotFoundException: Could not find a part of the path '/tmp/gq0eerpt.0j2'.
at System.IO.Enumeration.FileSystemEnumerator`1[[System.IO.FileSystemInfo, System.IO.FileSystem, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a]].CreateDirectoryHandle(String path, Boolean ignoreNotFound) in /_/src/libraries/System.IO.FileSystem/src/System/IO/Enumeration/FileSystemEnumerator.Unix.cs:line 79
at System.IO.Enumeration.FileSystemEnumerator`1[[System.IO.FileSystemInfo, System.IO.FileSystem, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a]].Init() in /_/src/libraries/System.IO.FileSystem/src/System/IO/Enumeration/FileSystemEnumerator.Unix.cs:line 39
at System.IO.Enumeration.FileSystemEnumerator`1[[System.IO.FileSystemInfo, System.IO.FileSystem, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a]]..ctor(String directory, Boolean
...
Here's a helix log from 44611 for reference.
This seemed to have happened at least 16 times in the last day.
Activity
danmoseley commentedon Nov 13, 2020
@eerhardt I can't look right now but didn't this recently change to stop polling? Maybe that made this more common?
eerhardt commentedon Nov 13, 2020
These tests were just changed with #41426.
cc @ericstj @maryamariyan
ericstj commentedon Nov 13, 2020
I’ll fix this. I introduced with the inotify test. What’s happening is that the timer thread doesn’t fire until after the test is done and disposing the watcher didn’t successfully cancel it. I had a fix for this but pulled it out after I stopped seeing the problem. For now the quickest fix is to move inotify test to outer loop.
stephentoub commentedon Nov 13, 2020
Reopening to track actually fixing the (now outerloop) test.
Related to #44652.
ericstj commentedon Nov 13, 2020
@stephentoub my intent was to use the new issue to track a better fix to the outerloop test.