Bug#812676: maven-scm: FTBFS - test fails with Unparseable date exception

[Michael Tautschnig]

Package: maven-scm
Version: 1.3-7
Severity: serious
Usertags: goto-cc

During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.

[...]
-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.apache.maven.scm.provider.synergy.consumer.SynergyCreateTaskConsumerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.472 sec - in org.apache.maven.scm.provider.synergy.consumer.SynergyCreateTaskConsumerTest
Running org.apache.maven.scm.provider.synergy.consumer.SynergyGetCompletedTasksConsumerTest
[ERROR] Wrong date format
java.text.ParseException: Unparseable date: "Wed Oct  4 15:42:47 2006"
	at java.text.DateFormat.parse(DateFormat.java:357)
	at org.apache.maven.scm.provider.synergy.consumer.SynergyGetCompletedTasksConsumer.consumeLine(SynergyGetCompletedTasksConsumer.java:114)
	at org.apache.maven.scm.provider.synergy.consumer.SynergyGetCompletedTasksConsumerTest.testSynergyGetCompletedTasksConsumer(SynergyGetCompletedTasksConsumerTest.java:53)
	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:606)
	at junit.framework.TestCase.runTest(TestCase.java:164)
	at junit.framework.TestCase.runBare(TestCase.java:130)
	at junit.framework.TestResult$1.protect(TestResult.java:106)
	at junit.framework.TestResult.runProtected(TestResult.java:124)
	at junit.framework.TestResult.run(TestResult.java:109)
	at junit.framework.TestCase.run(TestCase.java:120)
	at junit.framework.TestSuite.runTest(TestSuite.java:230)
	at junit.framework.TestSuite.run(TestSuite.java:225)
	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:606)
	at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:95)
	at org.apache.maven.surefire.junit.JUnit3Provider.executeTestSet(JUnit3Provider.java:131)
	at org.apache.maven.surefire.junit.JUnit3Provider.invoke(JUnit3Provider.java:108)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.14 sec <<< FAILURE! - in org.apache.maven.scm.provider.synergy.consumer.SynergyGetCompletedTasksConsumerTest
testSynergyGetCompletedTasksConsumer(org.apache.maven.scm.provider.synergy.consumer.SynergyGetCompletedTasksConsumerTest)  Time elapsed: 0.077 sec  <<< FAILURE!
junit.framework.AssertionFailedError: expected:<Wed Oct 04 15:42:47 UTC 2006> but was:<null>
	at junit.framework.Assert.fail(Assert.java:47)
	at junit.framework.Assert.failNotEquals(Assert.java:280)
	at junit.framework.Assert.assertEquals(Assert.java:64)
	at junit.framework.Assert.assertEquals(Assert.java:71)
	at org.apache.maven.scm.provider.synergy.consumer.SynergyGetCompletedTasksConsumerTest.testSynergyGetCompletedTasksConsumer(SynergyGetCompletedTasksConsumerTest.java:70)
[...]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 55.061 s
[INFO] Finished at: 2016-01-25T19:57:37+00:00
[INFO] Final Memory: 25M/1963M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on project maven-scm-provider-synergy: There are test failures.
[ERROR]
[ERROR] Please refer to /srv/jenkins-slave/workspace/sid-goto-cc-maven-scm/maven-scm-1.3/maven-scm-providers/maven-scm-provider-synergy/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 :maven-scm-provider-synergy
/usr/share/cdbs/1/class/maven.mk:127: recipe for target 'debian/stamp-maven-check' failed
make: *** [debian/stamp-maven-check] Error 1


The full build log is attached; please do let me know if the problem is
unreproducible, in which case I shall try to investigate further.

Best,
Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: maven-scm-build-log.txt.gz
Type: application/x-gunzip
Size: 31740 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20160125/a90b6041/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20160125/a90b6041/attachment-0001.sig>