|
||||||||
|
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/groups/opt_out.
Depending on how you configure your ant build, you may or may not run into the problem I'm describing above. Any change you can copy/paste the snippet of your ant build.xml that invokes your TestNG tests?
In your case, if I add a threshold field, you'll likely see a SUCCESS so long as your ant run does not terminate abnormally when it runs (i.e. - the ant exit code is non-zero). If it does, then you'll see a FAILURE. If you configure your ant build to fail when tests fails, then you'll always see a FAILURE (red) regardless of the new field that I'm adding. This is probably not the case for you since you said you get UNSTABLE (yellow) sometimes.
All that said, I'm happy to add the field, knowing that whether or not it functions as advertised is very specific to the build tool you're using to execute TestNG tests.
I'd like to know if Nalin has any opinion on this as the maintainer of the repo. I don't want to spend the time if the pull request won't be merged back into the mainline.