|
||||||||
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 |
[JIRA] (JENKINS-15322) NOTESTS in TAP response gives parse error and stack trace from plugin
alex.newn...@shazamteam.com (JIRA) Wed, 16 Jan 2013 06:00:03 -0800
- [JIRA] (JENKINS-15322) NOTESTS in TAP r... brunodepau...@yahoo.com.br (JIRA)
- [JIRA] (JENKINS-15322) NOTESTS in ... brunodepau...@yahoo.com.br (JIRA)
- [JIRA] (JENKINS-15322) NOTESTS in ... alex.newn...@shazamteam.com (JIRA)
JENKINS-16325 seems to be concerned with both
Using TAP plugin 1.9, I have not managed to get the stack trace when I only skip certain tests but I can duplicate the stack trace from the plugin when I append tests to one .tap file. I am not sure if multiple tests in one .tap file breaks the TAP spec (for a particular TAP version or perhaps all TAP versions).
So although the stack trace from this issue looks the same as the trace in JENKINS-16325, the reasons for the traces differ. However, the author of JENKINS-16325 mentions in his comments on that issue that he is still affected by JENKINS-16326 which does pretty much duplicate this issue.
My tests have been with the simplest TAP files possible, I may have missed some complexity, and I didn't use prove.
Hope this is useful!
Alex