severity 843038 wishlist
thanks
Hi,
The test that failed is CPU sensitive.
Yes, it should probably be disabled, but does not any "serious" bug if it
fails on a heavily loaded machine.
In particular, the solution obviously is to just not run the test at all.
That is not really an improvement either...
On Thu, Nov 3, 2016 at 12:16 PM, Santiago Vila <sanv...@unex.es> wrote:
> Package: src:elki
> Version: 0.7.1-2
> Severity: serious
>
> Dear maintainer:
>
> I tried to build this package in stretch with "dpkg-buildpackage -A"
> (which is what the "Arch: all" autobuilder would do to build it)
> but it failed:
>
> ------------------------------------------------------------
> --------------------
> [...]
> debian/rules build-indep
> dh build-indep --buildsystem=maven
> dh_testdir -i -O--buildsystem=maven
> dh_update_autotools_config -i -O--buildsystem=maven
> debian/rules override_dh_auto_configure
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> # Remove unneded executable bits:
> find elki addons data -type f -executable -exec chmod -x {} \+
> dh_auto_configure -O--buildsystem=maven
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar':
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar':
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar':
> No such file or directory
> mh_patchpoms -pelki --debian-build --keep-pom-version
> --maven-repo=/<<PKGBUILDDIR>>/debian/maven-repo
>
> [... snipped ...]
>
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec
> - in de.lmu.ifi.dbs.elki.evaluation.scores.ROCEvaluationTest
> Running de.lmu.ifi.dbs.elki.evaluation.scores.
> AveragePrecisionEvaluationTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec
> - in de.lmu.ifi.dbs.elki.evaluation.scores.AveragePrecisionEvaluationTest
> Running de.lmu.ifi.dbs.elki.evaluation.scores.MaximumF1EvaluationTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec
> - in de.lmu.ifi.dbs.elki.evaluation.scores.MaximumF1EvaluationTest
> Running de.lmu.ifi.dbs.elki.evaluation.paircounting.
> ClusterContingencyTableTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.019 sec
> - in de.lmu.ifi.dbs.elki.evaluation.paircounting.
> ClusterContingencyTableTest
>
> Results :
>
> Tests in error:
> IntegerArrayQuickSortTest.testSorted:130 TestTimedOut test timed out
> after 500...
>
> Tests run: 348, Failures: 0, Errors: 1, Skipped: 1
>
> [INFO] ------------------------------------------------------------
> ------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] ELKI Data Mining Framework - Parent Project ........ SUCCESS [
> 0.389 s]
> [INFO] ELKI Data Mining Framework ......................... FAILURE [02:01
> min]
> [INFO] ELKI Data Mining Framework - Batik Visualization ... SKIPPED
> [INFO] ELKI Data Mining Framework - Tutorial Algorithms ... SKIPPED
> [INFO] ELKI Data Mining Framework - LibSVM based extensions SKIPPED
> [INFO] ------------------------------------------------------------
> ------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------
> ------------
> [INFO] Total time: 02:02 min
> [INFO] Finished at: 2016-11-02T00:48:31+01:00
> [INFO] Final Memory: 14M/36M
> [INFO] ------------------------------------------------------------
> ------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:
> maven-surefire-plugin:2.17:test (default-test) on project elki: There are
> test failures.
> [ERROR]
> [ERROR] Please refer to /<<PKGBUILDDIR>>/elki/target/surefire-reports for
> the individual test results.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/
> MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn <goals> -rf :elki
> dh_auto_test: /usr/lib/jvm/java-8-openjdk-amd64/bin/java -noverify -cp
> /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/
> jvm/java-8-openjdk-amd64/lib/tools.jar -Dmaven.home=/usr/share/maven
> -Dmaven.multiModuleProjectDirectory=/<<PKGBUILDDIR>>
> -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/<<
> PKGBUILDDIR>>/debian/maven.properties
> org.codehaus.plexus.classworlds.launcher.Launcher
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<<PKGBUILDDIR>>/debian
> -Dmaven.repo.local=/<<PKGBUILDDIR>>/debian/maven-repo test returned exit
> code 1
> debian/rules:10: recipe for target 'build-indep' failed
> make: *** [build-indep] Error 1
> dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
> ------------------------------------------------------------
> --------------------
>
> I attach two different build logs.
>
> Apparently some test expect a certain task to be executed in a certain
> time. This is usually not a good idea for a Debian source package,
> because there is not any guarantee anywhere that the CPU performance
> will remain constant during the package build. The same machine could
> well be doing many other things in parallel.
>
> Thanks.
