miniflow added the comment:
After performing an strace - it shows that the underlying call to getcwd is
indeed returning ENOENT which is not correct. Does this become a libc bug?
--
___
Python tracker <rep...@bugs.python.org>
New submission from miniflow:
I am calling os.getcwd and am occasionally seeing failures inside my program.
This is not due to files missing as the files on the share are static.
Eror is:
[Errno 2] No such file or directory
Which is definitely not the case.
Can any sort of trace be done
