Your message dated Mon, 06 Nov 2006 04:02:08 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#396419: fixed in junitperf 1.9.1-5 has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---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 | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |
--- End Message ---
--- Begin Message ---Source: junitperf Source-Version: 1.9.1-5 We believe that the bug you reported is fixed in the latest version of junitperf, which is due to be installed in the Debian FTP archive: junitperf_1.9.1-5.diff.gz to pool/main/j/junitperf/junitperf_1.9.1-5.diff.gz junitperf_1.9.1-5.dsc to pool/main/j/junitperf/junitperf_1.9.1-5.dsc libjunitperf-java-doc_1.9.1-5_all.deb to pool/main/j/junitperf/libjunitperf-java-doc_1.9.1-5_all.deb libjunitperf-java_1.9.1-5_all.deb to pool/main/j/junitperf/libjunitperf-java_1.9.1-5_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Arnaud Vandyck <[EMAIL PROTECTED]> (supplier of updated junitperf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Mon, 6 Nov 2006 12:10:29 +0100 Source: junitperf Binary: libjunitperf-java-doc libjunitperf-java Architecture: source all Version: 1.9.1-5 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers <pkg-java-maintainers@lists.alioth.debian.org> Changed-By: Arnaud Vandyck <[EMAIL PROTECTED]> Description: libjunitperf-java - JUnit extensions for performance and scalability testing libjunitperf-java-doc - Documentation for libjunitperf-java Closes: 396419 Changes: junitperf (1.9.1-5) unstable; urgency=low . * built with java-gcj-compat-dev. * debian/rules: + removed ant-launcher.jar + removed the test target (closes: #396419) * Standards-Version: 3.7.2 (no change) Files: e5dbd5c397b67908c3bd020b7746de6b 782 libs optional junitperf_1.9.1-5.dsc 5088b3fb19a340da8d7c82e87cd8a4ae 2715 libs optional junitperf_1.9.1-5.diff.gz 24e7f625fa1814f5323a0b5073541336 18202 libs optional libjunitperf-java_1.9.1-5_all.deb 08cbad050589f4b9a0b03584d8629b8b 35444 doc optional libjunitperf-java-doc_1.9.1-5_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFTyKx4vzFZu62tMIRAiTuAJ9c9C7jCh9LAMAgctUCM2k9tQvm9ACguFrD hemOgWWNSYmfBynLLSRzIa8= =YhnL -----END PGP SIGNATURE-----
--- End Message ---
