Some worker bug
thempel opened this issue · comments
Any ideas what this is about? Just ran into it with the new master branch code. Excuse that the error messages are quadrupled due to the 4 Worker approach.
job.914608.txt
It always happens with a worker after one successful run, when starting the second run. I assume that #30 somehow removes the files that are being called.
Oh man, this one is real stupid...
The worker set the current directory to the worker.{,,,}/ directory and while being inside it is deleted.
No problem there. But if you now call any function (in the next task) that uses any os.getcwd() like os.path.abspath it fails.
The fix is easy...