![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Unassigned |
|
Components:
|
scala-junit-name-decoder |
|
Created:
|
21/Apr/14 7:57 PM
|
|
Description:
|
When a ScalaTest suite fails with "RUN ABORTED" exception using scalatest-maven-plugin, the Jenkins build shows as successful.
I believe the root cause of the issue is with Jenkins since if I run the Maven build on the command-line (with the same arguments as passed by Jenkins) it fails as expected.
See the related ScalaTest ticket with more details for recreating the issue: https://github.com/scalatest/scalatest/issues/297
I opened the ticket with ScalaTest as well as Jenkins since I believe the scalatest-maven-plugin could work around the issue.
As mentioned in the ScalaTest ticket, this seems related to: https://github.com/scalatest/scalatest/issues/273
.. which states that "The bottom line is that the build succeeds because no result xml files were written."
|
|
Environment:
|
Our Jenkins build server runs on 64-bit VM running Ubuntu 10.04. We are currently running Jenkins 1.537.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Donovan Levinson
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
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.
