Bug#396419: junitperf: FTBFS: failed tests (race condition ?)
Lucas Nussbaum
lucas at lucas-nussbaum.net
Tue Oct 31 17:07:16 UTC 2006
Package: junitperf
Version: 1.9.1-4
Severity: serious
Justification: FTBFS on i386, very likely to fail everywhere else
Usertags: grid5000
Hi,
During a rebuild of all packages in etch, I discovered that your package
failed to build on i386.
Relevant parts:
test-samples:
[junit] Testsuite: com.clarkware.junitperf.ExamplePerfTestSuite
[junit] Tests run: 121, Failures: 0, Errors: 0, Time elapsed: 20.338 sec
[junit] ------------- Standard Output ---------------
[junit] TimedTest (WAITING): testOneSecondResponse(com.clarkware.junitperf.ExampleTestCase): 1069 ms
[junit] TimedTest (WAITING): LoadTest (NON-ATOMIC): ThreadedTest: testOneSecondResponse(com.clarkware.junitperf.ExampleTestCase)(repeated): 19114 ms
[junit] ------------- ---------------- ---------------
[junit] Testcase: testOneSecondResponse took 1.014 sec
[junit] Testcase: testState took 0.013 sec
[junit] Testcase: testState took 0.006 sec
[junit] Internal error: caught an unexpected exception.
[junit] Testcase: testState took 0.006 sec
[junit] Testcase: testState took 0.006 sec
[junit] Testcase: testState took 0.004 sec
[junit] Please check your CLASSPATH and your installation.
[junit] java/lang/NullPointerException
[junit] Testcase: testState took 0.006 sec
[junit] Testcase: testState took 0.02 sec
[junit] Testcase: testState took 0.01 sec
[junit] Testcase: testState took 0.022 sec
[junit] Testcase: testState took 0.001 sec
[junit] Testcase: testState took 0.003 sec
[junit] Testcase: testState took 0.004 sec
[junit] Testcase: testState took 0.004 sec
[junit] Testcase: testState took 0.003 sec
[junit] Testcase: testState took 0.005 sec
[junit] Testcase: testState took 0.002 sec
[junit] Testcase: testState took 0.002 sec
[junit] Testcase: testState took 0.005 sec
[junit] Testcase: testState took 0.001 sec
[junit] Testcase: testState took 0.004 sec
[junit] Testcase: testOneSecondResponse took 1.004 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 1.004 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0.001 sec
[junit] Testcase: testOneSecondResponse took 1.002 sec
[junit] Testcase: testOneSecondResponse took 1.003 sec
[junit] Testcase: testOneSecondResponse took 0.001 sec
[junit] Testcase: testOneSecondResponse took 0.001 sec
[junit] Testcase: testOneSecondResponse took 1.001 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0.002 sec
[junit] Testcase: testOneSecondResponse took 1 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0.001 sec
[junit] Testcase: testOneSecondResponse took 0.001 sec
[junit] Testcase: testOneSecondResponse took 0.001 sec
[junit] Testcase: testOneSecondResponse took 0.002 sec
[junit] Testcase: testOneSecondResponse took 1 sec
[junit] Testcase: testOneSecondResponse took 1.001 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 1 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0.001 sec
[junit] Testcase: testOneSecondResponse took 0.002 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0.001 sec
[junit] Testcase: testOneSecondResponse took 0.001 sec
[junit] Testcase: testOneSecondResponse took 0.001 sec
[junit] Testcase: testOneSecondResponse took 0.997 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0.001 sec
[junit] Testcase: testOneSecondResponse took 0.003 sec
[junit] Testcase: testOneSecondResponse took 0.001 sec
[junit] Testcase: testOneSecondResponse took 0.002 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0.996 sec
[junit] Testcase: testOneSecondResponse took 0.996 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0.004 sec
[junit] Testcase: testOneSecondResponse took 0.004 sec
[junit] Testcase: testOneSecondResponse took 0.004 sec
[junit] Testcase: testOneSecondResponse took 0.003 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0.996 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0.004 sec
[junit] Testcase: testOneSecondResponse took 0.004 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0.003 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0.996 sec
[junit] Testcase: testOneSecondResponse took 1 sec
[junit] Testcase: testOneSecondResponse took 1 sec
[junit] Testcase: testOneSecondResponse took 0.001 sec
[junit] Testcase: testOneSecondResponse took 0.003 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 1 sec
[junit] Testcase: testOneSecondResponse took 1 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0.002 sec
[junit] Testcase: testOneSecondResponse took 0.001 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0.999 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0.003 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0.001 sec
[junit] Testcase: testOneSecondResponse took 0.999 sec
[junit] Testcase: testOneSecondResponse took 0.001 sec
[junit] Testcase: testOneSecondResponse took 0.003 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0.999 sec
[junit] Testcase: testOneSecondResponse took 0.001 sec
[junit] Testcase: testOneSecondResponse took 0.003 sec
[junit] Testcase: testOneSecondResponse took 0.003 sec
[junit] Testcase: testOneSecondResponse took 1 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0.004 sec
[junit] Testcase: testOneSecondResponse took 1 sec
[junit] Testcase: testOneSecondResponse took 0.004 sec
[junit] Testcase: testOneSecondResponse took 1.004 sec
BUILD FAILED
/build/root/junitperf-1.9.1/build.xml:82: Test com.clarkware.junitperf.ExamplePerfTestSuite failed
Total time: 29 seconds
make: *** [debian/stamp-ant-build] Error 1
******************************************************************************
Build finished at 20061031-1802
FAILED [dpkg-buildpackage died]
Purging /var/lib/schroot/mount/etch32-636552eb-2ae6-49c5-80a6-bbc7c77457f9/build/root/junitperf-1.9.1
It is important to note that the build did not fail each time: I built it 3 times, and it failed 2 times. So it is likely to be caused by a race condition or something.
About the archive rebuilt:
The rebuilt was done on about 60 AMD64 nodes of the Grid'5000 platform,
using a chroot containing an etch i386 environment (not unstable).
Internet was not accessible from the build nodes.
About Grid'5000:
The Grid'5000 project aims at building a highly reconfigurable
experimental Grid platform gathering 9 sites and featuring a total of
5000 CPUs. Its main purpose is to serve as an experimental testbed for
research in Grid Computing. To learn more about Grid'5000, read
https://www.grid5000.fr/
--
| Lucas Nussbaum
| lucas at lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lucas at nussbaum.fr GPG: 1024D/023B3F4F |
More information about the pkg-java-maintainers
mailing list