- Created Friday, December 19th 2014 @ 00:02:09
So, i did a quick search and did not find something related, but i am receiving nothing in the output log when my bot is tested. The strange thing is that the immediate io test actually runs the program and outputs like expected, but when it attempts the test match, nothing is in the output log. I have attempted reuploading my bot a few times, and oocationally the match runs, but still nothing in the output.
http://theaigames.com/competitions/warlight-ai-challenge-2/games/54934d6b4b5ab2019b8e6978/dump example output log if it can be seen =/
Any ideas on fixes?
- Created Friday, December 19th 2014 @ 00:54:14
I'm having the same issue with game http://theaigames.com/competitions/warlight-ai-challenge-2/games/549362c34b5ab2019b8e6a89
- Updated Friday, December 19th 2014 @ 02:20:46
Gunshin, I had the same issue due to debug info I was logging to stderr. I logged quite a lot of lines due to a bug causing a infini-loop.
P.S. A lot of your games never seem to finish see: http://theaigames.com/competitions/warlight-ai-challenge-2/game-log/GunshinBot/1, It might even be possible that these games are blocking the queue.
- Created Friday, December 19th 2014 @ 09:53:41
There was indeed a problem with the queue, which also caused no dump to be stored. Fixed now
- Created Friday, December 19th 2014 @ 12:58:56
- Created Friday, December 19th 2014 @ 13:36:21
Your bot is actually causing serious problems at the moment. I'm trying to figure out what is happening
- Created Friday, December 19th 2014 @ 14:01:42
I think I found the problem.. You probably have an infinite loop somewhere that causes your error dump to be HUGE. When the engine tries to save it, it results in an outOfMemoryError. I'm implementing something that catches it now, but try to fix your bot as well. I will take your bot out of ranked for now.
- Created Friday, December 19th 2014 @ 14:52:42
Issue should be fixed now
- Created Friday, December 19th 2014 @ 15:01:55
Thanks for the quick fix, you're the man jim.
Maybe you should also consider some kind of memory barrier for the bots. I once had a bug that caused the bot to consume arbitrary amounts of memory and crashed the site for a brief period. In the log it stated that the testcase took 360 seconds. ( Sorry for that, by the way )
Bots with such erroneous behaviour ( consuming too much memory, timing out, not exiting properly... ) should be disabled automatically until another version is uploaded I think. Also Bots with a faulty exitcode ( like when they segfault ) shouldn't keep the engine waiting and be disabled.
How are the bots terminated currently? I've built a function that terminates it in an orderly fashion when it receives "EXIT" through the standard inputstream.
- Updated Friday, December 19th 2014 @ 15:32:37
Crashing bots, etc should be handled correctly and keep the deamon that is emptying the queue running. However in some rare cases like the above, an error slips through. This is why we have the Beta label for this competition, because you always run into unexpected stuff, especially because I rewrote the part of the engine that communicates with the bots. Also the map generator sometimes had some unexpected outputs, which caused the engine to crash, but that should all be fixed now.
Thank you for your consideration, but I expect there are no more problems from now on.
- Created Friday, December 19th 2014 @ 19:44:44
Yeah, i thought it was not an infinite loop due to the fact that the match would continue, until i realised i was just being a retard. My bot is fixed, and it was only in ranked play because i accidentally clicked on 'set'. At least i found a potential abuse though? =S