[sage-devel] unit-testing parallel code

['Reimundo Heluani' via sage-devel]

Hello, I'm implementing a worker pool using Python's multiprocessing module. My tests run fine under the Sage interactive interpreter or the Jupyter notebook, but they fail with a MemoryError as if I have ran out of available threads when running the unit tests with "sage -t"

RuntimeError: can't start new thread


--
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/20200725124550.GA142944%40vertex.

I suppose this is because "sage -t" open new processes before running the tests. Where in the code should I start looking to debug this, I'd like to implement this in a way that the actual tests are run by "sage -t". I mean I could bypass this problem by checking if the current process is the main process before forking the worker pool, but the problem of this approach is that the environment would be different on a run of "sage -t" and on a run in the interactive interpreter, so I would lose the functionality of the docstring tests. Best, R.

signature.asc
Description: PGP signature