Difference between revisions of "Thread:Talk:Gilgalad/Minibot?/reply (10)"

From Robowiki
Jump to navigation Jump to search
m
m
Line 1: Line 1:
 
Yes, I run 2 clients. More specifically 2 machines, both of which run roborumble and meleerumble, one of this additionally runs meleeTop30. As far as I can see, they have identical relevant software configuration.
 
Yes, I run 2 clients. More specifically 2 machines, both of which run roborumble and meleerumble, one of this additionally runs meleeTop30. As far as I can see, they have identical relevant software configuration.
  
I will try to isolate a problem. I left running only one computer with meleerumble and roborumble. Let's see if the currently running is a guilty one.
+
I do not get it: microrumble and nanorumble seems to be fine with either of the clients, but minirumble is populated with megabots. Any idea what is going on?
  
Edit1: one client seems to be fine. I see 271 bots in nanorumble and they all seems to be nano
+
As fat as I see after some tests, it is not a particular client issue. At start up, either of the clients cleans the mess, i.e. removes bogus entries. But then as it runs, it reintroduces them.
  
Edit2: I do not get it, nanorumble seems to be fine with either of the clients, but minirumble is populated
+
I will report it to Fnl again.
with megabots. Any idea what is going on?
 
 
 
Edit3: note to yourself, "l" client definitely messes up minirumble, client "b" seems to be fine. But they are identical, as far as I can see.  Also, both clients complain "Could not load properties file: ./roborumble/files/codesize1v1.txt"
 

Revision as of 17:37, 6 September 2014

Yes, I run 2 clients. More specifically 2 machines, both of which run roborumble and meleerumble, one of this additionally runs meleeTop30. As far as I can see, they have identical relevant software configuration.

I do not get it: microrumble and nanorumble seems to be fine with either of the clients, but minirumble is populated with megabots. Any idea what is going on?

As fat as I see after some tests, it is not a particular client issue. At start up, either of the clients cleans the mess, i.e. removes bogus entries. But then as it runs, it reintroduces them.

I will report it to Fnl again.