farnulfo / ai-contest

Automatically exported from code.google.com/p/ai-contest
0 stars 0 forks source link

No error message and lost game #199

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. You can look at this game: 
http://ai-contest.com/visualizer.php?game_id=5864984
2. The game stopped at turn 107 with barabanus loss though the victory 
condition isn't achieved and barabanus had much more ships than his adversary.

What is the expected output? What do you see instead?
The game should have been continued. The game stopped instead without any clue 
why the game was lost.

Please provide any additional information below.
There're many games that bots lose without any error message, though they would 
definitely win the game having much more ships than the adversary.

All those games are reported when worker=0

Look at this forum thread for more games from other players: 
http://ai-contest.com/forum/viewtopic.php?f=18&t=888

Original issue reported on code.google.com by buratin....@gmail.com on 13 Oct 2010 at 6:39

GoogleCodeExporter commented 9 years ago
The possible reason could be "not enough memory".
May be the contest rules should be updated with memory use restriction?
My bot sometimes uses up to 38M in the middle of the game.
May be that's why it crashes: not enough memory?

Original comment by buratin....@gmail.com on 19 Oct 2010 at 9:49

GoogleCodeExporter commented 9 years ago
Worker 0 is the main game server, and the others are cloud servers.  At this 
time, only cloud servers do error reporting.  The game end is probably due to a 
timeout.

Original comment by jklan...@gmail.com on 24 Oct 2010 at 2:52

GoogleCodeExporter commented 9 years ago
Here is a patch to add support for error reporting to the trunk engine.  It is 
only part of the solution.

Original comment by jklan...@gmail.com on 24 Oct 2010 at 3:38

Attachments:

GoogleCodeExporter commented 9 years ago
Here is a patch for error reporting in the tournament manager.  Both patches 
are totally untested.

Original comment by jklan...@gmail.com on 24 Oct 2010 at 4:52

Attachments:

GoogleCodeExporter commented 9 years ago
After adding a small fix to the patch, this is now fixed in revision 455. 
Thanks jklandis.

Original comment by janzert on 24 Oct 2010 at 6:39