Hi,Yvan Fournier wrote: ↑Mon Aug 01, 2022 5:53 pm Hello,
I'll check the code. We have never encountered this issue, but I wonder whether it might be due to latency/delays in the filesystem operation leading to a directory not being empty yet. Not sure, just guessing, but I'll see if I can make the code more robust there.
In the meantime, as a workaround, you can use the advanced checkpoint/restart settings in the GUI so as to have only one checkpoint at the end of the computation. This should avoid going through the path that causes the error.
Best regards,
Yvan
My cluster doesn't support GUI. I'm wondering if I could set the checkpoint/restart settings without GUI?
Best regards.