Re: [Rails-devel] Release Rails 1.6.3 available

[Erik V. <eri...@xs...>]

> > However the existing 1835 and a new test case I have added
> > fail now. This is most likely related to the Clemens variant change of
> > player priority and rerunning several 1835 in one instance, however
> > this usually indicates some probability that it is not undo-proof.
> >
> > So let us wait for you coming back to solve this jointly.
> 
> I haven't looked at the non-standard 1835 variants for a long time, so
it's
> good to have a test case now.
> I only see 1835_NatDoubleShare failing, all other cases are OK.  Do you
have
> more failures?

I don't understand why JUnit does things different from normal running.

The report expects:

BuysItemFor,T3,M5,80
FloatsWithCash,M5,80
BuysItemFor,T2,M1,80  <===
FloatsWithCash,M1,80
BuysItemFor,T1,M3,80
FloatsWithCash,M3,80

and that is exactly what happens in a normal run (extract from log):

2012-02-14 21:08:25 INFO   T3 buys M5 for 80M  (ReportBuffer addMessage 186)

2012-02-14 21:08:25 INFO   M5 floats and receives 80M  (ReportBuffer
addMessage 186) 
2012-02-14 21:08:25 INFO   T2 buys M1 for 80M  (ReportBuffer addMessage 186)
<===
2012-02-14 21:08:25 INFO   M1 floats and receives 80M  (ReportBuffer
addMessage 186) 
2012-02-14 21:08:25 INFO   T1 buys M3 for 80M  (ReportBuffer addMessage 186)

2012-02-14 21:08:25 INFO   M3 floats and receives 80M  (ReportBuffer
addMessage 186) 

so I'm amazed that the JUnit report says that >>T1<< has bought M3 in its
test run.

junit.framework.ComparisonFailure: Reports differ in line 13
expected:<BuysItemFor,T[2],M1,80> but was:<BuysItemFor,T[1],M1,80>

where line 13 corresponds to the lines where I added arrows.

I'm lost.

Erik.