[
https://issues.apache.org/jira/browse/JDO-765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239535#comment-16239535
]
Tilmann Zäschke edited comment on JDO-765 at 11/5/17 1:33 PM:
--------------------------------------------------------------
The problem was that it would only abort the current configuration file, but
proceed executing the other .conf files. This should be fixed now (patch v2:
[^JDO-765-patch-v2.txt]), thanks for testing.
was (Author: tilmann):
The problem was that it would only abort the current configuration file, but
proceed executing the other .conf files. This should be fixed now (patch v2),
thanks for testing.
> TCK should fail if tests fail
> -----------------------------
>
> Key: JDO-765
> URL: https://issues.apache.org/jira/browse/JDO-765
> Project: JDO
> Issue Type: Bug
> Reporter: Tilmann Zäschke
> Priority: Trivial
> Attachments: JDO-765-patch-v2.txt
>
>
> Currently, TCK test failures are reported to the console and in the logs, but
> the Maven build still succeeds.
> The proposal is to make the behavior configurable, the default being that the
> Maven build fails if any TCK tests fail.
> The new configuration option would be called "-Djdo.tck.onFailure" and have
> the following options:
> * "failFast" will immediately abort the test run.
> * "failEventually" (default) will execute the whole TCK before failing.
> * "logOnly" will report failures to console and logs only but return
> 'SUCCESS' to the Maven execution environment.
> Attached is a patch with an implementation of the proposed changes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
