Infinite loop with multiprocessing

[samtygier-stfc]

Infinite loop with multiprocessing

[mrbean-bremen]

Not really. The problem is the mixture of faked on non-faked calls, e.g. the usage of faked descriptors in the real fs and vice verse. Even if you would map this into the fake fs, the returned descriptors would still be from the real fs (due to the C calls), which do not exist in the fake fs (or if they do exist, they point to something else, which could lead to all kinds of undefined behavior).
Sometimes it makes sense to pause patching in a test, execute something in the real fs, and resume patching again, but this won't work in this case.
It could be possible to write a fake version of posixshmem and patch the usage accordingly, but I think this wouldn't work either because of other problems in multiprocessing. The biggest problem is probably that the fake fs will not work in spawed processes in principle - and as these are the point of multiprocessing, I see no real way to fix this - sorry!

[mrbean-bremen]

Unfortunately, this won't work, at least not out of the box, due to the limitations of pyfakefs. Multiprocessing is one of the modules not playing nice with pyfakefs due to the use of system C functions to access the file system. In this case, it uses posixshmem, which is a C module, to access the shared memory. This will work in the real filesystem, so either the file is not found, or if the file exists there, a real file descriptor is returned, which is not found in the fake filesystem.

I could not reproduce the inifinite loop so far, but I got another error related to the mentioned problem. Currently, I don't have a solution for this (other than patching it away).

[samtygier-stfc]

Thanks for having a look.
Is there a way to allow this to pass through to the real filesystem? I tried self.fs.add_real_directory("/dev/shm/",read_only=False) which did not help.
It looks like the point in resource_tracker.py where this fails is with a pipe in a spawned process.

[mrbean-bremen]

I'm moving this to the "limitations" discussions, as there is nothing we can do here, as far as I cn see.