After some tests with version 0.7.3, I encountered this "has no side" warning. This is the first time I encountered it and actually stopped the whole match before it is finished.
Started game 332 of 1000 (Cheng_4.39_x64 vs D2015.1.252)
Finished game 330 (Hakkapeliitta 3.0 x64 vs D2015.1.252): 1-0 {White wins by adj
udication}
Finished game 331 (D2015.1.252 vs Cheng_4.39_x64): 1/2-1/2 {Draw by adjudication
} Warning: Player HIARCS 14 WCSC has no side
Finished game 332 (Cheng_4.39_x64 vs D2015.1.252): 1/2-1/2 {Draw by insufficient
mating material}
Started game 335 of 1000 (D2015.1.252 vs Hannibal 1.1 64bit) Warning: Player HIARCS 14 WCSC has no side
Finished game 335 (D2015.1.252 vs Hannibal 1.1 64bit): 1/2-1/2 {Draw by insuffic
ient mating material}
Started game 336 of 1000 (Hannibal 1.1 64bit vs D2015.1.252)
Finished game 336 (Hannibal 1.1 64bit vs D2015.1.252): 1/2-1/2 {Draw by insuffic
ient mating material}
Started game 337 of 1000 (D2015.1.252 vs Quazar_0.4_x64)
Here is a compile for windows with following changes. This is still unreleased but code changes are already available. I think these changes are significant, so just for those interested.
1. Fix FEN tag in the header of a game. Now the FEN has hmvc and fmvn.
Sample.
2. (windows) Make sure engines are killed along with CuteChess.
Now even with Control+break (was only control+C) keys to interrupt the running tour, engines are exited/quited/killed along with cutechess.
Be aware the version number is still 0.7.2 when you send the command cutechess-cli -version.
I have not encountered problems with this update version so far. It is encourage to report problems, warning messages and others if ever you encounter one. This would help the developers to further improve the tool.
Ferdy wrote:2. (windows) Make sure engines are killed along with CuteChess.
Now even with Control+break (was only control+C) keys to interrupt the running tour, engines are exited/quited/killed along with cutechess.
Will it also completely terminate processes still hogging memory? I'm using 0.7.1 and the only tournament that really works is "match". As soon as you have 3 or more engines, both gauntlet and round-robin will ignore the "restart" parameter; no matter what option you specify, engines will be restarted, and the "terminated" processes will still be using memory:
- a few dozens will still be requiring the full 100% they peaked at (Working set as reported by Resource Monitor)
- the rest will occupy a modicum of 20K, which amounts to quite a bit when they number in the thousands (RAMMap)
In the end, you run out of memory and the tournament is exited abruptly.