- Created Monday, May 16th 2016 @ 09:28:59
http://theaigames.com/competitions/go/games/573972904ca8010a70cc6f92/dump GoGewBagBot vs RustyGo (133 rounds, latest game as of this posting) Is there any way to tell if a bot times out unexpectedly if the issue is with the bot hanging up on some piece of code unexpectedly/unusually, or if the server running the bot hung up causing the bot to stop responding (through no fault of its own)?
Doesn't matter much at this point, but curious if you have any way of verifying in the future when it will matter. Also would be nice to know for determining if there is a problem that needs to be found and fixed (by me, with my bot) or if I can simply let it be.
Bot had full time bank up to end when it became unresponsive.
DeveloperCreated Tuesday, May 17th 2016 @ 08:52:46
We currently have no way to see the exact cause if there is nothing in the error dump. But it's unlikely that it's a server problem, though it is possible of course.
- Created Wednesday, June 1st 2016 @ 21:39:20
Still not sure what causes my bot to stop working on your servers as I've never seen it happen locally, but it continues to happen irregularly. Is it possible my bot's use of multiple threads is causing it to run on a thread shared by another process that may at times delay my bot's processing causing the timeouts seen?
DeveloperCreated Thursday, June 2nd 2016 @ 08:44:46
I think it happens because your bot sometimes violates the chroot jail limits. But it's very had to tell you exactly what the limits are sadly. The multiple threading might be the cause.
- Created Thursday, June 2nd 2016 @ 21:29:49
Never heard of chroot jail limits before so don't know anything about them besides what I just quickly looked up and am not sure how I could be causing such a type of issue. I don't try to access any files or anything like that. Unless the base starter bot has the issue and it isn't something I explicitly added, but revealed by using more. I'm uploading a new version (V31) that uses fewer threads to see if that makes any difference as that's the only thing I added that I can think of which may do something irregular with the system's resources (along with using a locker object to prevent thread race issues). If my bot were exceeding stack size limits or something harder to detect like that would that possibly cause the occasional issue? Bot doesn't use that much memory, but stuff like that I've noticed can be pretty irregular and hard to detect. Thanks for the response.
- Created Saturday, June 4th 2016 @ 00:33:20
Looks like my latest version using only 4 threads didn't help. I've used the unofficial engine to run my bot locally some (as well as using similar code in c++ for the parts I added to the starter bot), but have never seen it hang or get stuck or not 'survive' a game as the unofficial engine denotes at the end of each game. So haven't been able thus far to reproduce the problem locally, which is why I thought it might be a quirk of running on your engine. Do you know if anyone else's bot has this issue of infrequent timeouts? Going to have to experiment with cutting out parts of my code to see if I can narrow down the troublesome section.
- Created Saturday, June 4th 2016 @ 04:21:43
Looking back at my bot's history it looks like it's probably due to some changes I made in version 23 of my bot as the previous versions never had the issue as far as I could tell. So probably just my bot as you suggested from the start. Will look at the changes I made on that version to see if I can narrow down what is causing the issue.