Thread history

From User talk:VoidBot
Viewing a history listing
Jump to navigation Jump to search
Time User Activity Comment
16:23, 8 April 2013 Skilgannon (talk | contribs) New thread created  
16:25, 8 April 2013 Voidious (talk | contribs) New reply created (Reply to Why not roborumble?)
16:28, 8 April 2013 Skilgannon (talk | contribs) New reply created (Reply to Why not roborumble?)
16:39, 8 April 2013 Voidious (talk | contribs) New reply created (Reply to Why not roborumble?)
16:49, 8 April 2013 Voidious (talk | contribs) New reply created (Reply to Why not roborumble?)
18:01, 8 April 2013 Voidious (talk | contribs) New reply created (Reply to Why not roborumble?)

Why not roborumble?

It isn't generating archived rankings for roborumble, any idea why? All bots have 988 pairings.

Skilgannon16:23, 8 April 2013

I noticed some bots had 989 pairings again yesterday. I went to check again a few minutes ago and let you know about it, since that would hold up the archive, but I see that they're at 988 now. Maybe that just fixed itself today? It checks every hour so I'll kick it when I get home if it hasn't run by then.

Voidious16:25, 8 April 2013
 

The rumble's been stable for a few hours now (I actually fixed that bug with the extra bots this time... I hope) and I saw a server log 15 mins ago of it requesting, so it is definitely running.

Skilgannon16:28, 8 April 2013
 

That was probably the Twitter one, which runs every 15 mins. The rumble archiver should be at the top of the hour. It's possible I turned off the "roborumble" last week when I ran it manually or something... I'll check it when I get home.

Voidious16:39, 8 April 2013

On that note, I wonder what's up with the Twitter one... Either it shouldn't be checking the rumble server because of no new participants, or if it has participants that it's watching, it should have seen the rumble was stable and tweeted them.

Voidious16:49, 8 April 2013
 

Ok, summary:

  • The archiver saw pairings incomplete for a few hours, then hit a parsing error - I don't know exactly what happened. I ran it manually and it worked.
  • The tweeter was set to 2800 battles for 1v1, so it has a couple bots that it's watching. Brought that back down to 2000 for now until we get the min roborumble battles back to like 3k.
  • Starting up my clients again.
Voidious18:01, 8 April 2013