What do you think about a GigaMeleeRumble?
← Thread:Talk:RoboRumble/Rule Suggestions/What do you think about a GigaMeleeRumble?/reply (21)
Good idea with the littlerumble. I've disabled the app for now, I can set that up tomorrow and copy data across, then re-enable the app.
I'd rather have only one version for submitting battles, simply because we don't know all the bugs yet. It is better to make the chosen version easily available than to allow possibly different versions to submit battles.
I see a lot of errors like this:
java.io.FileNotFoundException: http://literumble.appspot.com/UploadedResults Unable to upload results meleerumble,35,1000x1000,beaming,1399046843566,SERVER ntc.Opposite 1.5,9870,3207,0 spinnercat.Omen 1.0,6542,1976,0
Am I the only one?
The app is disabled until I get a chance to copy the data over to another app which won't allow uploads, which will be tomorrow evening. So you can pause clients until then.
Another question.
What is the official java version to be used with robocode?
I personally use java 6 but I think some bots are compiled with java 7 and do not run on my machine. Shall I switch to java 7?
If you're using Sun/Oracle Java, I would strongly argue you should not be using Java 6 anymore, and should not have been for the last year, because you're not getting security updates.
If you're using OpenJDK instead of the Sun/Oracle version, you can still get security updates for Java 6, so that isn't an issue.
As OpenJDK 6 doesn't have official Windows builds, and Sun/Oracle Java 6 does not get security updates, perhaps it is best to as a rule not be using any version of Java 6 (even if it has recent security patches) for Roborumble, as new Windows users submitting bots cannot easily test with Java 6.
Literumble is up and running, accepting 1.9.2.0 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
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page.
Return to Thread:Talk:RoboRumble/Rule Suggestions/What do you think about a GigaMeleeRumble?/reply (36).
It seems to be stuck at 'queue full' most of the time.
Regarding the same bot pair added multiple times, perhaps you're referring to how it has to upload once for each rumble that's fitting for the pair of bots? (i.e. the different size categories)
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 1.9.1.0 fixed a bug with the codesize generation. Which Robocode version are you running?