Re: Build failed in Jenkins: the 4547 machine gun #53

2013-01-25 Thread Adrien Grand
On Fri, Jan 25, 2013 at 2:30 AM, Robert Muir rcm...@gmail.com wrote: I think the bug is when its direct and the last block has the optimized bitsPerValue=0 case. Right. This was a test bug due to the fact that the reader moves the file pointer in the for (i = 0; i valueCount; ++i) { assert

Build failed in Jenkins: the 4547 machine gun #53

2013-01-24 Thread Charlie Cron
See http://fortyounce.servebeer.com/job/the%204547%20machine%20gun/53/ -- [...truncated 969 lines...] [junit4:junit4] [junit4:junit4] Suite: org.apache.lucene.search.spans.TestSpanExplanationsOfNonMatches [junit4:junit4] Completed on J3 in 0.10s, 31 tests

Re: Build failed in Jenkins: the 4547 machine gun #53

2013-01-24 Thread Robert Muir
In all cases the test failure is because we somehow write 100 wasted bytes: assertEquals(in1.getFilePointer(), in1.length()); I'm sure it will drive Adrien crazy :) 2013/1/24 Charlie Cron hudsonsevilt...@gmail.com: See http://fortyounce.servebeer.com/job/the%204547%20machine%20gun/53/

Re: Build failed in Jenkins: the 4547 machine gun #53

2013-01-24 Thread Robert Muir
I think the bug is when its direct and the last block has the optimized bitsPerValue=0 case. On Thu, Jan 24, 2013 at 8:24 PM, Robert Muir rcm...@gmail.com wrote: In all cases the test failure is because we somehow write 100 wasted bytes: assertEquals(in1.getFilePointer(), in1.length());