|
||||||||
|
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 r... [email protected] (JIRA)
- [JIRA] (JENKINS-15322) NOTESTS in ... [email protected] (JIRA)
- [JIRA] (JENKINS-15322) NOTESTS in ... [email protected] (JIRA)
- [JIRA] (JENKINS-15322) NOTESTS in ... [email protected] (JIRA)
- [JIRA] (JENKINS-15322) NOTESTS in ... [email protected] (JIRA)
- [JIRA] (JENKINS-15322) NOTESTS in ... [email protected] (JIRA)
- [JIRA] (JENKINS-15322) NOTESTS in ... [email protected] (JIRA)
- [JIRA] (JENKINS-15322) NOTESTS in ... [email protected] (JIRA)
- [JIRA] (JENKINS-15322) NOTESTS in ... [email protected] (JIRA)
- [JIRA] (JENKINS-15322) NOTESTS in ... [email protected] (JIRA)
- [JIRA] (JENKINS-15322) NOTESTS in ... [email protected] (JIRA)

Hmm, the output doesn't look like a valid TAP stream., it looks to be something specific to a Perl module or prove tool.
In order to have a TAP output, I think you can do something similar to perl -Ilib /opt/performance/scripts/t/dbcoststest1.t
This should give you something like
1..0
I found this perl command in this blog post [1] some time ago. Maybe it will help to clarify what is happening with the plug-in, there's some interesting comments there.
[1] http://blogs.perl.org/users/confuseacat/2011/09/perl-testing-with-jenkinshudson-avoiding-some-pitfalls.html