#903125 exec-maven-plugin: FTBFS: tests fail with (expected:<[mvn] --version> but was:<['mvn'] --version>) #903125
- Package:
- src:exec-maven-plugin
- Source:
- exec-maven-plugin
- Submitter:
- Santiago Vila
- Date:
- 2021-01-11 21:09:03 UTC
- Severity:
- important
- Tags:
Dear maintainer: I tried to build this package in stretch + security + stretch-proposed-updates but it failed: -------------------------------------------------------------------------------- [...] debian/rules build-indep test -x debian/rules mkdir -p "." /usr/share/maven-debian-helper/copy-repo.sh /<<BUILDDIR>>/exec-maven-plugin-1.1.1+dfsg/debian 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 -plibmaven-exec-plugin-java --debian-build --keep-pom-version --maven-repo=/<<BUILDDIR>>/exec-maven-plugin-1.1.1+dfsg/debian/maven-repo --build-no-docs touch debian/stamp-poms-patched # before-build target may be used to unpatch the pom files, so we need to check if # patching the pom files is needed here, normally not if [ ! -f pom.xml.save ]; then \ /usr/bin/make -f debian/rules patch-poms; \ fi [... snipped ...] testOverrides(org.codehaus.mojo.exec.ExecMojoTest) Time elapsed: 0.043 sec <<< FAILURE! junit.framework.ComparisonFailure: expected:<[mvn] -f pom.xml> but was:<['mvn'] -f pom.xml> at junit.framework.Assert.assertEquals(Assert.java:81) at junit.framework.Assert.assertEquals(Assert.java:87) at org.codehaus.mojo.exec.ExecMojoTest.checkMojo(ExecMojoTest.java:371) at org.codehaus.mojo.exec.ExecMojoTest.testOverrides(ExecMojoTest.java:331) testOverrides3(org.codehaus.mojo.exec.ExecMojoTest) Time elapsed: 0.035 sec <<< FAILURE! junit.framework.ComparisonFailure: expected:<[mvn] --version> but was:<['mvn'] --version> at junit.framework.Assert.assertEquals(Assert.java:81) at junit.framework.Assert.assertEquals(Assert.java:87) at org.codehaus.mojo.exec.ExecMojoTest.checkMojo(ExecMojoTest.java:371) at org.codehaus.mojo.exec.ExecMojoTest.testOverrides3(ExecMojoTest.java:340) Running org.codehaus.mojo.exec.ExecJavaMojoTest Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.241 sec - in org.codehaus.mojo.exec.ExecJavaMojoTest Results : Failed tests: org.codehaus.mojo.exec.ExecMojoTest#testRunOK ComparisonFailure expected:<[mvn... org.codehaus.mojo.exec.ExecMojoTest#testRunFailure ComparisonFailure expected:... org.codehaus.mojo.exec.ExecMojoTest#testRunError ComparisonFailure expected:<[... org.codehaus.mojo.exec.ExecMojoTest#testOverrides ComparisonFailure expected:<... org.codehaus.mojo.exec.ExecMojoTest#testOverrides3 ComparisonFailure expected:... Tests run: 14, Failures: 5, Errors: 0, Skipped: 0 [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 14.291 s [INFO] Finished at: 2018-07-06T13:15:30+00:00 [INFO] Final Memory: 19M/90M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on project exec-maven-plugin: There are test failures. [ERROR] [ERROR] Please refer to /<<BUILDDIR>>/exec-maven-plugin-1.1.1+dfsg/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 /usr/share/cdbs/1/class/maven.mk:127: recipe for target 'debian/stamp-maven-check' failed make: *** [debian/stamp-maven-check] Error 1 dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2 -------------------------------------------------------------------------------- The build was made with "dpkg-buildpackage -A" but I guess that's not relevant at all in this case. Apparently some build-dependency in security or stretch-proposed-updates changed behaviour in a way that makes the tests to break, but I'm not sure a reassign would be a good thing here. Thanks.
This is also reproducible in jessie: ... ------------------------------------------------------- T E S T S ------------------------------------------------------- Running org.codehaus.mojo.exec.ExecJavaMojoTest Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.492 sec Running org.codehaus.mojo.exec.ExecMojoTest [debug] Toolchains are ignored, 'executable' parameter is set to target/java [debug] got arguments from system properties: -f pom.xml Tests run: 7, Failures: 5, Errors: 0, Skipped: 0, Time elapsed: 0.124 sec <<< FAILURE! Results : Failed tests: testRunOK(org.codehaus.mojo.exec.ExecMojoTest): expected:<[mvn] --version> but was:<['mvn'] --version> testRunFailure(org.codehaus.mojo.exec.ExecMojoTest): expected:<[mvn] --version> but was:<['mvn'] --version> testRunError(org.codehaus.mojo.exec.ExecMojoTest): expected:<[mvn] --version> but was:<['mvn'] --version> testOverrides(org.codehaus.mojo.exec.ExecMojoTest): expected:<[mvn] -f pom.xml> but was:<['mvn'] -f pom.xml> testOverrides3(org.codehaus.mojo.exec.ExecMojoTest): expected:<[mvn] --version> but was:<['mvn'] --version> Tests run: 14, Failures: 5, Errors: 0, Skipped: 0 [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] There are test failures. Please refer to /build/exec-maven-plugin-1.1.1+dfsg/target/surefire-reports for the individual test results. [INFO] ------------------------------------------------------------------------ [INFO] For more information, run Maven with the -e switch [INFO] ------------------------------------------------------------------------ [INFO] Total time: 14 seconds [INFO] Finished at: Mon Jul 16 16:46:31 UTC 2018 [INFO] Final Memory: 22M/608M [INFO] ------------------------------------------------------------------------ /usr/share/cdbs/1/class/maven.mk:87: recipe for target 'mvn-build' failed make: *** [mvn-build] Error 1 Andreas
Control: severity -1 important Buster/Sid is not affected. Since there is also a simple workaround for stable and oldstable (disabling the tests), I am going to lower the severity to important. Markus
Please don't do that sort of thing. A package is considered to have a FTBFS bug, serious and RC, if the exit status of dpkg-buildpackage is > 0, indicating error, for whatever reason which is not the fault of the person building the package (including of course failing the tests). If you believe severities of FTBFS bugs should be lower than serious in case it's the tests the ones to fail, then please make a proposal to make all FTBFS bugs of "grave" severity as a general rule, then and only then it would make sense to downgrade from grave to serious. Thanks.