Open ahmedselim2017 opened 15 hours ago
Yeah, that's probably it, I have seen it before but it only hapened when I ran like 50 jobs at once :D
If you like, I can implement filelock to lock the log files while reading/writing, as a job crashing may cause wasted resources if unchecked.
Hi, I was running multiple runs parallelly on multiple GPUs with the same output folder and one of the runs exited with the error below when fixing interface residues.
The runs continued for more than 3 days without an error, and this error has only occurred once. Given the infrequency of the error, is it possible that it is caused by a race condition where one run tries to read a file while the other one is using it?