You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Executables still occasionally 'disappear' even when using LxFS alone within the lxss directory in my AppData on my boot drive. This happens much, much more frequently on a drive mounted using DrvFS as mentioned in issue #2464 but, unfortunately, it still occurs on LxFS too, though much less often.
This occurs once or twice during my cross-compilation of a large suite of utilities and libraries. Progress on a native GNU/Linux box does not fail. The source code may be cloned here.
During compilation, the following error very occasionally occurs (once every ten hours or so):
x86_64-w64-mingw32-gcc: error: : No such file or directory
...whereas the file x86_64-w64-mingw32-gcc is very much there upon inspection, in the executable path, and has the executable attribute set. Resuming compilation from the point of failure succeeds. Occasionally, a later failure may result. The compilation as a whole takes some 24 hours on this machine (8 cores, 16GB RAM, 4.2GHz SkyLake processor). All disk tests pass, all memory tests pass. This compilation is quite heavy on filesystem bashing.
Here is the full error. There is no strace. I do not think I have the room for a strace output for this enormous compilation.
On Build 16281.rs3_release.170829-1438:
Executables still occasionally 'disappear' even when using LxFS alone within the lxss directory in my AppData on my boot drive. This happens much, much more frequently on a drive mounted using DrvFS as mentioned in issue #2464 but, unfortunately, it still occurs on LxFS too, though much less often.
This occurs once or twice during my cross-compilation of a large suite of utilities and libraries. Progress on a native GNU/Linux box does not fail. The source code may be cloned here.
During compilation, the following error very occasionally occurs (once every ten hours or so):
x86_64-w64-mingw32-gcc: error: : No such file or directory
...whereas the file
x86_64-w64-mingw32-gcc
is very much there upon inspection, in the executable path, and has the executable attribute set. Resuming compilation from the point of failure succeeds. Occasionally, a later failure may result. The compilation as a whole takes some 24 hours on this machine (8 cores, 16GB RAM, 4.2GHz SkyLake processor). All disk tests pass, all memory tests pass. This compilation is quite heavy on filesystem bashing.Here is the full error. There is no strace. I do not think I have the room for a strace output for this enormous compilation.
The text was updated successfully, but these errors were encountered: