Open albertz opened 10 months ago
The scrambled output means that there are many processes here stopped at the same time by SIGINT.
The graph computations are using a ThreadPool (https://github.com/rwth-i6/sisyphus/blob/master/sisyphus/graph.py#L232C12-L232C12). I guess you get this output if you hit Ctrl-C while these computations are running. This problem might go away if you set gs.GRAPH_WORKER=1, but you would also use the multithreading speed up if your filesystem has a higher latency.
Are you saying GRAPH_WORKER=1
is anyway always better and we can remove the old code which handles GRAPH_WORKER>1
?
I'm not searching for workarounds. Also, I could simply just ignore this message.
I simply report this because I think it's bad if the process crashes with terminated by signal SIGABRT
, and maybe this should be investigated further.
No, I'm not saying GRAPH_WORKER=1
is better, it's just a workaround which in most cases makes sisyphus slower.
Sometimes, but not always (maybe 20% of the cases?), when I hit Ctrl+C, I get this crash: