Closed SpheMakh closed 3 years ago
Any errors above that? (Maybe put the full log on pastebin?)
BrokenProcessPool is just fancy speak for a subprocess (probably the I/O one, looking at the context) segfaulting or running out of memory (how much you got?) or otherwise blowing up. It may be cryptic, but it's already an improvement on just hanging there (see e.g. https://github.com/ratt-ru/CubiCal/issues/439), which older versions of concurrent.futures did. We should add an exception handler to print a prettier message though.
I had memory on the previous run, then tweaked a few but got this instead. The machine has 188Gb total memory
Full log is here https://pastebin.com/Mhiu6M9s
It goes away after I tweaked some of the dist-<foo>
options. Indeed, a prettier error message telling the user to adjust dist-<foo>
options will do
I'll work on a better error as part of https://github.com/ratt-ru/CubiCal/issues/439. It's a bit tricky to catch when subprocesses just die on you with no warning, as they do for out-of-memory...
Should I close this?
Yeah it's a duplicate of #439 effectively.
I'm not sure how to describe this, except for saying it happened. Has anyone seen it before