- Created Sunday, November 29th 2015 @ 14:56:07
I'm getting this strange error in my test output:
Java HotSpot(TM) 64-Bit Server VM warning: No monotonic clock was available - timed services may be adversely affected if the time-of-day clock changes
I'm also noticing that any calls to random methods always return the same thing, I'm wondering if a seed can't be found through date time services. Is this a deliberate attempt to stop bots from having any randomness? If not do we think this is correlated to the randomness problem I'm seeing and could it be fixed?
- Created Sunday, November 29th 2015 @ 23:31:37
I got similar error, my bot, which is the default one in JAVA doesn't load. I have 3 java files in one zip file. Am i doing something wrong? I put my error below:
Java HotSpot(TM) 64-Bit Server VM warning: No monotonic clock was available - timed services may be adversely affected if the time-of-day clock changes Error: Could not find or load main class BotStarter
Input dump Output dump Running testcase /opt/aigames/etc/testsfourinarow/testfourinarow.txt... Testing Bot with setup input... ... finished testcase in 0.170000001788 seconds Test failed: no output
DeveloperCreated Monday, November 30th 2015 @ 09:19:34
The bots run from a chroot jail, which causes the warning and can't be fixed. But it shouldn't affect anything in your bot.
@ishakir: The starterbots all implement randomness and don't have this problem, so I'm not sure what causes yours.
@karrakis: Make sure you set the classpaths rights, that seems to be your problem
- Created Monday, November 30th 2015 @ 09:35:17
It works already.
- Updated Sunday, December 13th 2015 @ 11:15:49
I have a related problem in C, where calling clock() on the server always returns 0, even though it works fine on my machine.
This is a problem as I'm using it to manage how much time is spent searching for moves depending on how much time is left in the timebank.
This is especially jarring as a prior version of my bot was seemingly able to use clock() without problems.
EDIT: This only applies for testing input; In actual games and whatnot, everything seems to work just fine. However, when testing input, a bot will timeout if it doesn't respond immediately after getting 'action move'.