What do you think about a GigaMeleeRumble?
← Thread:Talk:RoboRumble/Rule Suggestions/What do you think about a GigaMeleeRumble?/reply (31)
Literumble is up and running, accepting 220.127.116.11 contributions. There is a static copy of the old data at staticrumble.appspot.com. I'll keep an eye on it from my side, and please let me know if you see any issues with your clients. In a few days, when we're sure everything is working, I'll delete the data and we can start from fresh.
All my clients show in rumble and meleerumble
OK. Queue full,Wisdom vs GridFu discarded.
naturally, with different bots name.
There is something fishy, since than I see the same bot pair added to queue over and over with messages like this
OK. Wisdom vs GridFu added to queue in 41ms
Still something is fishy, on one of my clients I see multiple (like 100) attempt to do something with stat uploading. Currently the following happening, first I bunch of "queue is full" than
OK. Queue full,Tidus vs Zealot discarded.
for this pair of bots.
Above error are for the rumble client, I also run the meleerumble on the same machine and that one complains about Wisdom vs GridFu as in above message, with similar numerous attempts.
What is strange is that the other rumble client seems to behave proper on the other machine. Both machines have identical installations of robocode and java.
You do not have permission to edit this page, for the following reason:
The action you have requested is limited to users in the group: Users.
You can view and copy the source of this page:
The reason the queue is full so much is that uploads are happening at a rate of ~35/s, but I can only process ~5/s. I'll work more on optimising load and store times, but there is only so much I can do with that...
Uh... somebody's client is misconfigured, and uploading a bunch of stuff to the Minirumble which doesn't belong.
For example, "simonton.beta.LifelongObsession 0.5.1" is a Megabot.
Can folks who are currently contributing check that their client isn't doing this please?
Beaming, looking at logs it seems to be coming from one of your clients. I see in the Robocode release notes that 18.104.22.168 fixed a bug with the codesize generation. Which Robocode version are you running?