Strings of timelosses under cutechess-cli
Posted: Wed Aug 01, 2018 3:07 am
I have the following output from a cutechess session https://pastebin.com/raw/JpHAX8tJ
Interestingly, the first 7951 games had no problems, and neither did the next ~6000.
My #1 worry is that this is the fault of Ethereal, which I find highly suspect. Outside input would be appreciated.
Assuming it is not Ethereal, the issue must either be with Cutechess or with my actual machine.
To further confuse things, I have played 2,008,484 games on my testing framework without having a time loss. Those are played in batches of 250.
Any thoughts? Similar experience?
Thanks
EDIT: Both blocks of time losses are 30 games each. I was playing with concurrency 30, meaning 60 engines running at once. This suggests that at some point, every single engine hanged. Then cutechess restarted the first 30. Then the 2nd set of 30 crashed, where restarted, and then all went on smoothly.
Interestingly, the first 7951 games had no problems, and neither did the next ~6000.
My #1 worry is that this is the fault of Ethereal, which I find highly suspect. Outside input would be appreciated.
Assuming it is not Ethereal, the issue must either be with Cutechess or with my actual machine.
To further confuse things, I have played 2,008,484 games on my testing framework without having a time loss. Those are played in batches of 250.
Any thoughts? Similar experience?
Thanks
EDIT: Both blocks of time losses are 30 games each. I was playing with concurrency 30, meaning 60 engines running at once. This suggests that at some point, every single engine hanged. Then cutechess restarted the first 30. Then the 2nd set of 30 crashed, where restarted, and then all went on smoothly.