maven-scm version 1.3-4 failed to build with openjdk-7

Bug #888979 reported by James Page on 2011-11-11
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
maven-scm (Ubuntu)
Undecided
Unassigned

Bug Description

During a rebuild test on precise with default-jdk switched to openjdk-7, a build failure was detected for maven-scm version 1.3-4.

See attached log for full build failure details.

This log snippet might also be of interest:

 at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:601)
 at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:96)
 at org.apache.maven.surefire.junit.JUnit3Provider.executeTestSet(JUnit3Provider.java:117)
 at org.apache.maven.surefire.junit.JUnit3Provider.invoke(JUnit3Provider.java:94)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:601)
 at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
 at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
 at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
 at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107)
 at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68)
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.064 sec
Running org.apache.maven.scm.provider.perforce.command.remove.PerforceRemoveConsumerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec
Running org.apache.maven.scm.provider.perforce.command.remove.PerforceRemoveCommandTest
[WARNING] Username as part of path is deprecated, the new format is scm:perforce:[username@]host:port:path_to_repository
[WARNING] Username as part of path is deprecated, the new format is scm:perforce:[username@]host:port:path_to_repository
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.061 sec

Results :

Failed tests: testGetCommandLine(org.apache.maven.scm.provider.perforce.command.changelog.PerforceChangeLogCommandTest): expected:<...ngelog-command-test []changes -t ...> but was:<...ngelog-command-test [-c foo ]changes -t ...>

Tests run: 52, Failures: 1, Errors: 0, Skipped: 0

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] There are test failures.

Please refer to /«PKGBUILDDIR»/maven-scm-providers/maven-scm-provider-perforce/target/surefire-reports for the individual test results.
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 minute 21 seconds
[INFO] Finished at: Fri Nov 11 01:10:56 UTC 2011
[INFO] Final Memory: 114M/351M
[INFO] ------------------------------------------------------------------------
make: *** [mvn-build] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
────────────────────────────────────────────────────────────────────────────────
Build finished at 20111111-0110

Finished
────────

E: Build failure (dpkg-buildpackage died)

tags: added: amd64 auto java7-ftbfs
James Page (james-page) on 2011-11-25
tags: added: test
James Page (james-page) wrote :

Reconfirmed in Ubuntu Quantal - adding ftbfs tag.

tags: added: ftbfs
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments