[
https://issues.jenkins-ci.org/browse/JENKINS-13927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163705#comment-163705
]
Bruno P. Kinoshita commented on JENKINS-13927:
----------------------------------------------
This one? "else if (status != null && status == StatusValues.NOT_OK)"
I have a staged alpha version, that I was just trying to finish one last
feature before releasing it. I will release this version this week, so we can
test this issue again to see if it is still happening. How does that sound? :-)
Thanks
> TAP: Failed test does not set build to failed.
> ----------------------------------------------
>
> Key: JENKINS-13927
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13927
> Project: Jenkins
> Issue Type: Bug
> Components: tap
> Environment: Jenkins ver. 1.461
> Jenkins TAP Plugin 1.2.8
> Reporter: Lance Wicks
> Assignee: Bruno P. Kinoshita
> Labels: plugin
> Attachments: TAP_BUG.png
>
>
> When the "Failed tests mark build as failure" option is activated on a job
> that runs on a jenkins slave, the TAP display shows a failed test
> The Jenkins build itself still shows as a success however.
> See attached screenshot. Notice TAP chart shows failures, but build history
> shows successful builds.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
