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

[Markus Koschany]

Control: tags -1 pending

I have rebuilt the package multiple times but I could not reproduce the
build failure. The tests are still enabled but we ignore possible test
failures for now. Manual inspection is required.

If it was a bigger issue we would have seen other fall-out by now.



signature.asc
Description: OpenPGP digital signature

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

[Santiago Vila]

On Mon, 25 Jan 2016, Michael Tautschnig wrote:

> java.text.ParseException: Unparseable date: "Wed Oct  4 15:42:47 2006"

This happened to me today while checking for "dpkg-buildpackage -A" bugs.
I attach my build log.

> 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.

The problem seems to be random. I guess that if you try to build many
times, a small fraction of the times will fail with the same error.

I would say there is a real problem here, so if you have time and
motivation, go ahead and investigate.

We want package builds to always succeed, not just "most of the time",
so bugs that only happen in a random way are also bugs.

Thanks.

maven-scm_1.3-7_amd64-20160826T002925Z.gz
Description: application/gzip

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: 
but was:
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  -rf :maven-scm-provider-synergy