[ https://issues.jenkins-ci.org/browse/JENKINS-12616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159326#comment-159326 ]
Thomas Fürer commented on JENKINS-12616: ---------------------------------------- it is the same behavior if I set a threshold of Build Status Total New Total New Thresholds: 1 1 10 10 I'm using the file attached which has only one failing test. > Tests failes but the job is still OK > ------------------------------------ > > Key: JENKINS-12616 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12616 > Project: Jenkins > Issue Type: Bug > Components: xunit > Environment: jenkins 1.445 > xunit 1.34 > Ubuntu server 11.11 > Reporter: Thomas Fürer > Assignee: gbois > Priority: Blocker > Attachments: boost-config.PNG, failedButOK.PNG, TEST-failed.xml > > > just use the attached result file with BOOST > the error is listed correct in the test report, but the job is still OK but > need to be at least UNSTABLE. > As you can see in the screenshot I do not have any thresholds set. > I do not have any example at the moment, but I think we have this problem > also with NUnit tests. -- 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