added some wrap around code to help debug why failures at referee/player side happend. The referee logs are formatted in a way they won't start with a digit, so on this assumption one can distinguish them from expected player output (number representing player's score).
Surely one needs to test referee and players separately, but some errors appear rarely and only get visible once running hundreds of test with brutaltester, so it's nice to have the option. In case of referee crashes there is no log file for that game (at least that was my experience with CoK).
Hi @dreignier,
added some wrap around code to help debug why failures at referee/player side happend. The referee logs are formatted in a way they won't start with a digit, so on this assumption one can distinguish them from expected player output (number representing player's score).
Surely one needs to test referee and players separately, but some errors appear rarely and only get visible once running hundreds of test with brutaltester, so it's nice to have the option. In case of referee crashes there is no log file for that game (at least that was my experience with CoK).
Also line 106 shows now which player failed.
Btw. my CoK referee for brutalster (I started a pull towards original CoK repo already): https://github.com/fala13/code-of-kutulu and all the stuff for CoK compiled: https://github.com/fala13/CoK_artifacts