Bug#450422: easymock: FTBFS: tests blocked

[Michael Koch]

On Sat, Jan 12, 2008 at 03:48:31PM +0100, Philipp Kern wrote:
> On Wed, Nov 07, 2007 at 10:21:27AM +0100, Lucas Nussbaum wrote:
> > It blocked during the testcases. I have no idea why. The last testcases
> > to be executed were:
> >     [junit] Testcase: setOpenCallCountTwice took 0.045 sec
> >     [junit] Testcase: setIllegalMinimumCount took 0.001 sec
> >     [junit] Testcase: setIllegalMaximumCount took 0.001 sec
> >     [junit] Testcase: setMinimumBiggerThanMaximum took 0.001 sec
> >     [junit] Running org.easymock.tests.RecordStateInvalidReturnValueTest
> >     [junit] Testsuite: org.easymock.tests.RecordStateInvalidReturnValueTest
> >     [junit] Tests run: 11, Failures: 0, Errors: 0, Time elapsed: 0.023 sec
> >     [junit] Tests run: 11, Failures: 0, Errors: 0, Time elapsed: 0.023 sec
> >     [junit] 
> >     [junit] Testcase: setInvalidBooleanReturnValue took 0.013 sec
> >     [junit] Testcase: setInvalidLongReturnValue took 0.001 sec
> >     [junit] Testcase: setInvalidFloatReturnValue took 0.001 sec
> >     [junit] Testcase: setInvalidDoubleReturnValue took 0 sec
> >     [junit] Testcase: setInvalidObjectReturnValue took 0.001 sec
> >     [junit] Testcase: setInvalidBooleanReturnValueCount took 0.001 sec
> >     [junit] Testcase: setInvalidLongReturnValueCount took 0.001 sec
> >     [junit] Testcase: setInvalidFloatReturnValueCount took 0.001 sec
> 
> Not reproducible as-is, but fails later in my amd64 unstable sbuild:
> 
> dh_installdocs -plibeasymock-java-doc  debian/README.Debian-source Documentation*.html easymock.css samples api  
> find: invalid predicate `)('
> dh_installdocs: command returned error code
> make: *** [binary-install/libeasymock-java-doc] Error 1
> dpkg-buildpackage: failure: /usr/bin/fakeroot debian/rules binary gave error exit status 2
> ******************************************************************************
> Build finished at 20080112-1537
> FAILED [dpkg-buildpackage died]

I can't reproduce this bug too. But I can't reproduce this build failure
either. The package builds fine for me.

Lucas: can you try to reproduce this error?


Cheers,
Michael