[JIRA] [junit-plugin] (JENKINS-34407) junit-plugin parse error

2016-04-30 Thread ogon...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oliver Gondža commented on  JENKINS-34407 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: junit-plugin parse error  
 
 
 
 
 
 
 
 
 
 
Pushed 1.13 with the fix. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [junit-plugin] (JENKINS-34407) junit-plugin parse error

2016-04-30 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34407 
 
 
 
  junit-plugin parse error  
 
 
 
 
 
 
 
 
 

Change By:
 
 SCM/JIRA link daemon 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [junit-plugin] (JENKINS-34407) junit-plugin parse error

2016-04-30 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-34407 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: junit-plugin parse error  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Oliver Gondža Path: src/main/java/hudson/tasks/junit/CaseResult.java src/main/java/hudson/tasks/junit/SuiteResult.java src/main/java/hudson/tasks/junit/TimeToFloat.java src/test/java/hudson/tasks/junit/SuiteResultTest.java src/test/resources/hudson/tasks/junit/junit-report-testsuite-time-attrs.xml http://jenkins-ci.org/commit/junit-plugin/e09cdd41a020533af124be8bd8baaba3d9a3f1df Log: Merge pull request #43 from jenkinsci/parse-time-in-suiteresult 
[FIXED JENKINS-34407] Parse time correctly in SuiteResult. 
Compare: https://github.com/jenkinsci/junit-plugin/compare/2952d092b9d7...e09cdd41a020 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [junit-plugin] (JENKINS-34407) junit-plugin parse error

2016-04-27 Thread a...@iisn.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 André Fügenschuh updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34407 
 
 
 
  junit-plugin parse error  
 
 
 
 
 
 
 
 
 

Change By:
 
 André Fügenschuh 
 
 
 
 
 
 
 
 
 
 Upgrading the junit-plugin from 1.11 to 1.12 fails with a parse error.I guess this relates to "PR #35" because the *skipped* (Ignore attr.) test result file's "time" attr. is *empty*.While the originator of the file (NUnit) should store a meaningful default (like  -  "00:00:00" - "0.0" ), its up to the consumer to provide robust parsing, either by ignoring the "skipped" tests at all or by ignoring the empty string.// Jenkins log stacktrace\[16:48:06.879\] ERROR: Step ‘Publish NUnit test result report’ aborted due to exception: \[16:48:06.879\] java.io.IOException: Failed to read C:\Jenkins\workspace\Foo\temporary-junit-reports\TEST-Bar.Common.Test.Utils.AccessorTest_13_2.xml\[16:48:06.879\]  at hudson.tasks.junit.TestResult.parse(TestResult.java:306)\[16:48:06.879\]  at hudson.tasks.junit.TestResult.parsePossiblyEmpty(TestResult.java:244)\[16:48:06.879\]  at hudson.tasks.junit.TestResult.parse(TestResult.java:175)\[16:48:06.879\]  at hudson.tasks.junit.TestResult.parse(TestResult.java:154)\[16:48:06.879\]  at hudson.tasks.junit.TestResult.(TestResult.java:126)\[16:48:06.879\]  at hudson.plugins.nunit.NUnitPublisher$1.invoke(NUnitPublisher.java:243)\[16:48:06.879\]  at hudson.plugins.nunit.NUnitPublisher$1.invoke(NUnitPublisher.java:226)\[16:48:06.879\]  at hudson.FilePath.act(FilePath.java:990)\[16:48:06.879\]  at hudson.FilePath.act(FilePath.java:968)\[16:48:06.879\]  at hudson.plugins.nunit.NUnitPublisher.getTestResult(NUnitPublisher.java:226)\[16:48:06.879\]  at hudson.plugins.nunit.NUnitPublisher.recordTestResult(NUnitPublisher.java:189)\[16:48:06.879\]  at hudson.plugins.nunit.NUnitPublisher.perform(NUnitPublisher.java:152)\[16:48:06.879\]  at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)\[16:48:06.879\]  at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782)\[16:48:06.879\]  at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723)\[16:48:06.879\]  at hudson.model.Build$BuildExecution.post2(Build.java:185)\[16:48:06.879\]  at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668)\[16:48:06.879\]  at hudson.model.Run.execute(Run.java:1763)\[16:48:06.879\]  at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)\[16:48:06.879\]  at hudson.model.ResourceController.execute(ResourceController.java:98)\[16:48:06.879\]  at hudson.model.Executor.run(Executor.java:410)\[16:48:06.879\] Caused by: java.lang.NumberFormatException: empty String\[16:48:06.879\]  at sun.misc.FloatingDecimal.readJavaFormatString(Unknown Source)\[16:48:06.879\]  at sun.misc.FloatingDecimal.parseFloat(Unknown Source)\[16:48:06.879\]  at java.lang.Float.parseFloat(Unknown Source)\[16:48:06.879\]  at hudson.tasks.junit.SuiteResult.(SuiteResult.java:170)\[16:48:06.879\]  at hudson.tasks.junit.SuiteResult.parseSuite(SuiteResult.java:144)\[16:48:06.879\]  at hudson.tasks.junit.SuiteResult.parse(SuiteResult.java:129)\[16:48:06.879\]  at hudson.tasks.junit.TestResult.parse(TestResult.java:301)\[16:48:06.879\]  ... 20 more// UnitTest.result file

[JIRA] [junit-plugin] (JENKINS-34407) junit-plugin parse error

2016-04-27 Thread a...@iisn.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 André Fügenschuh commented on  JENKINS-34407 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: junit-plugin parse error  
 
 
 
 
 
 
 
 
 
 
All comments following my OP are related to the fact that the parsing is not L10N capable. While its a good idea that the originator should not store a localized formatted number, the consumer could parse with a localized NumberFormat instance. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [junit-plugin] (JENKINS-34407) junit-plugin parse error

2016-04-27 Thread crussel...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chris Russell edited a comment on  JENKINS-34407 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: junit-plugin parse error  
 
 
 
 
 
 
 
 
 
 Jenkins: 2.0Java: jdk1.8.0_45   , jdk1.7.0_79   The same is occurring for me in cases of long-running jobs. This does not occur after downgrading to version 1.11 of the plugin. It looks like the root cause was likely identified here: https://github.com/jenkinsci/junit-plugin/commit/dabb301a90215849123437c61a9027ef2bd76703#diff-c17f918d04dfda506bcad39a3b390b26 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [junit-plugin] (JENKINS-34407) junit-plugin parse error

2016-04-27 Thread crussel...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chris Russell commented on  JENKINS-34407 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: junit-plugin parse error  
 
 
 
 
 
 
 
 
 
 
Jenkins: 2.0 Java: jdk1.8.0_45  
The same is occurring for me in cases of long-running jobs. This does not occur after downgrading to version 1.11 of the plugin.  
It looks like the root cause was likely identified here: https://github.com/jenkinsci/junit-plugin/commit/dabb301a90215849123437c61a9027ef2bd76703#diff-c17f918d04dfda506bcad39a3b390b26 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [junit-plugin] (JENKINS-34407) junit-plugin parse error

2016-04-26 Thread martin.weg...@ebp.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Martin Wegner commented on  JENKINS-34407 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: junit-plugin parse error  
 
 
 
 
 
 
 
 
 
 
Same problem here: 

 

Tests run: 54, Failures: 1, Errors: 0, Skipped: 3

[ERROR] There are test failures.

Please refer to C:\Jenkins\workspace\bla\target\surefire-reports for the individual test results.
[JENKINS] Recording test results
java.io.IOException: Failed to read C:\Jenkins\workspace\bla\target\surefire-reports\TEST-bla.test.TestBlub.xml
	at hudson.tasks.junit.TestResult.parse(TestResult.java:306)
	at hudson.tasks.junit.TestResult.parsePossiblyEmpty(TestResult.java:244)
	at hudson.tasks.junit.TestResult.parse(TestResult.java:213)
	at hudson.maven.reporters.SurefireArchiver.postExecute(SurefireArchiver.java:148)
	at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoEnded(Maven3Builder.java:634)
	at hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:615)
	at hudson.maven.Maven3Builder$JenkinsEventSpy.onEvent(Maven3Builder.java:308)
	at org.apache.maven.eventspy.internal.EventSpyDispatcher.onEvent(EventSpyDispatcher.java:108)
	at org.apache.maven.eventspy.internal.EventSpyExecutionListener.mojoSucceeded(EventSpyExecutionListener.java:131)
	at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87)
	at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:227)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
	at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
	at org.jvnet.hudson.maven3.launcher.Maven32Launcher.main(Maven32Launcher.java:132)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238)
	at jenkins.maven3.agent.Maven32Main.launch(Maven32Main.java:186)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:136)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:71)
	at hudson.remoting.UserRequest.perform(UserRequest.java:120)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:332)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at 

[JIRA] [junit-plugin] (JENKINS-34407) junit-plugin parse error

2016-04-25 Thread r...@otit.fi (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Risto Oikarinen commented on  JENKINS-34407 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: junit-plugin parse error  
 
 
 
 
 
 
 
 
 
 
I'm also seeing this with 1.12: 

Caused by: java.lang.NumberFormatException: For input string: "1,152.814" at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:2043) at sun.misc.FloatingDecimal.parseFloat(FloatingDecimal.java:122) at java.lang.Float.parseFloat(Float.java:451) at hudson.tasks.junit.SuiteResult.(SuiteResult.java:170)
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [junit-plugin] (JENKINS-34407) junit-plugin parse error

2016-04-22 Thread a...@iisn.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 André Fügenschuh created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34407 
 
 
 
  junit-plugin parse error  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 junit-plugin 
 
 
 

Created:
 

 2016/Apr/23 2:12 AM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 André Fügenschuh 
 
 
 
 
 
 
 
 
 
 
Upgrading the junit-plugin from 1.11 to 1.12 fails with a parse error. I guess this relates to "PR #35" because the skipped (Ignore attr.) test result file's "time" attr. is empty. While the originator of the file (NUnit) should store a meaningful default (like "00:00:00"), its up to the consumer to provide robust parsing, either by ignoring the "skipped" tests at all or by ignoring the empty string. 
// Jenkins log stacktrace [16:48:06.879] ERROR: Step ‘Publish NUnit test result report’ aborted due to exception:  [16:48:06.879] java.io.IOException: Failed to read C:\Jenkins\workspace\Foo\temporary-junit-reports\TEST-Bar.Common.Test.Utils.AccessorTest_13_2.xml [16:48:06.879] at hudson.tasks.junit.TestResult.parse(TestResult.java:306) [16:48:06.879] at hudson.tasks.junit.TestResult.parsePossiblyEmpty(TestResult.java:244) [16:48:06.879] at hudson.tasks.junit.TestResult.parse(TestResult.java:175) [16:48:06.879] at hudson.tasks.junit.TestResult.parse(TestResult.java:154) [16:48:06.879] at hudson.tasks.junit.TestResult.(TestResult.java:126) [16:48:06.879] at hudson.plugins.nunit.NUnitPublisher$1.invoke(NUnitPublisher.java:243) [16:48:06.879] at hudson.plugins.nunit.NUnitPublisher$1.invoke(NUnitPublisher.java:226) [16:48:06.879] at hudson.FilePath.act(FilePath.java:990) [16:48:06.879] at hudson.FilePath.act(FilePath.java:968) [16:48:06.879] at