[JIRA] (JENKINS-15322) NOTESTS in TAP response gives parse error and stack trace from plugin
Bruno P. Kinoshita resolved JENKINS-15322 as Fixed NOTESTS in TAP response gives parse error and stack trace from plugin Fixed. Will release in 2.0 with JENKINS-17245. Change By: Bruno P. Kinoshita (16/Mar/13 2:51 PM) Status: Open Resolved Resolution: Fixed 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.
[JIRA] (JENKINS-15322) NOTESTS in TAP response gives parse error and stack trace from plugin
Bruno P. Kinoshita stopped work on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin Change By: Bruno P. Kinoshita (16/Mar/13 2:50 PM) Status: In Progress Open 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.
[JIRA] (JENKINS-15322) NOTESTS in TAP response gives parse error and stack trace from plugin
Bruno P. Kinoshita commented on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin Wiki updated. Created the section "Running Perl tests with prove" with an example of how one can run prove and archive its output. The procedure is the same even if you use NOTESTS in TAP. You can follow the instructions there, but there's another bug which causes the plug-in to not list tests which plan is marked as skip all. The remaining work will continue there, please feel free to comment there. Both issues will be released together in 2.0. 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.
[JIRA] (JENKINS-15322) NOTESTS in TAP response gives parse error and stack trace from plugin
Bruno P. Kinoshita commented on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin The link to the bug fixed in tap4j: https://github.com/tupilabs/tap4j/issues/13 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.
[JIRA] (JENKINS-15322) NOTESTS in TAP response gives parse error and stack trace from plugin
Bruno P. Kinoshita commented on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin Yay! There are some broken links, and seems like they had to restore an old backup. I'll add tap4j information and examples there again. As a side note, I believe I've fixed this issue, but as I had to fix tap4j parser, I'll use a few more hours to test it. I'll update the Wiki with information on how to use the plug-in with prove --archive and an example with skip_all. 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.
[JIRA] (JENKINS-15322) NOTESTS in TAP response gives parse error and stack trace from plugin
Bruno P. Kinoshita started work on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin Change By: Bruno P. Kinoshita (15/Mar/13 2:06 PM) Status: Open In Progress 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.
[JIRA] (JENKINS-15322) NOTESTS in TAP response gives parse error and stack trace from plugin
Bruno P. Kinoshita stopped work on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin Change By: Bruno P. Kinoshita (15/Mar/13 2:06 PM) Status: In Progress Open 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.
[JIRA] (JENKINS-15322) NOTESTS in TAP response gives parse error and stack trace from plugin
Bruno P. Kinoshita started work on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin Change By: Bruno P. Kinoshita (15/Mar/13 2:06 PM) Status: Open In Progress 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.
[JIRA] (JENKINS-15322) NOTESTS in TAP response gives parse error and stack trace from plugin
Alex Newnham commented on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin Update: Excellent news! http://testanything.org/ is back up and running. 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.
[JIRA] (JENKINS-15322) NOTESTS in TAP response gives parse error and stack trace from plugin
Alex Newnham commented on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin I can't see a use case for multiple TAP streams within a single file. None of my TAP is in this format so it's not a feature I am looking for. thanks Alex 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.
[JIRA] (JENKINS-15322) NOTESTS in TAP response gives parse error and stack trace from plugin
Bruno P. Kinoshita commented on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin Hi @Alex, IN JENKINS-16325 a user suggested: prove *.t --archive tap/ That worked fine for me. One TAP Strem (in this case, a TAP file) cannot, or at least should not, contain multiple TAP files. In TAP specification a blank line in a file is ignored, as well as any non-TAP related token. So we would have to write a special parser to handle multiple TAP files within a single file. I would prefer avoid that if possible. Let me know if that works for you too. Thanks! /B 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.
[JIRA] (JENKINS-15322) NOTESTS in TAP response gives parse error and stack trace from plugin
Bruno P. Kinoshita updated JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin Change By: Bruno P. Kinoshita (27/Feb/13 12:24 PM) Status: Reopened Open 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.
[JIRA] (JENKINS-15322) NOTESTS in TAP response gives parse error and stack trace from plugin
Alex Newnham commented on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin JENKINS-16325 seems to be concerned with both skipping certain tests appending TAP output from iterating thru multiple .t test files and output to one .tap file. 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 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
Bruno P. Kinoshita commented on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin Hi Alex, Do you know if this issue is related to JENKINS-16325, please? If so, maybe I can link both issues as related here so you would get update notifications from both. Thanks, Bruno 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
Bruno P. Kinoshita commented on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin Hi Alex, nice finding, I'll use web.archive.org for now. I've got in touch with some guys from the tap-l mailing list, and one of them forwarded the message to other mailing lists and to the responsible of testanything.org. Hopefully it will be back online in few days. In the meantime, I will try to find out more about TAP 12, and why Tap::Harness does not output TAP 13 :o) Thanks a lot. 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 Newnham commented on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin http://testanything.org has been down for A Very Long Time, it seems. There's a crawled version of the site here: http://web.archive.org/web/20100124210854/http://testanything.org/wiki/index.php/Main_Page Browsing from there, I noticed here that Every test set as defined in this document should contain a version definition. A test set without a version definition is assumed to be written in TAP version 12, which is not covered by this document. Unfortunately I haven't yet found a definition for TAP version 12, but at least http://web.archive.org has a definition of TAP 13. It might be safe to assume that the Perl Tap::Harness module is writing valid TAP 12 - also that without a version specifier > 12 the TAP plugin for Jenkins should parse TAP as TAP 12. Maybe I can coerce my perl harness to output TAP 13 which would probably be a fix to my problem, but in the meantime some of the above may be useful to you? 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
Bruno P. Kinoshita commented on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin > Perhaps there's a mismatch here somewhere between the TAP produced by our Test::More module and Tap::Harness and the TAP specifications. Or maybe the plugin is expecting a different TAP version? Probably. The plug-in is expecting TAP 13, thought TAP 12 syntax was more similar to TAP 13, but never worked with this version. > Currently I can't investigate further as http://testanything.org is down at the moment. The site has been down for over a week. I'll drop an e-mail to the mailing list and hopefully someone will fix it. >In our projects we can't easily switch to using prove from the command line or a bash script as our .t files aren't static, they rely on a whole bunch of variable being passed into them via the TAP::Harness, there may be other workarounds possible though. Sounds like an interesting case. I don't have Perl in this computer (got a new one) but I will try something from this blog post [1]. In case you have some spare time to take a look on this and see if anything makes sense... my Perl skills are quite limited [1] http://www.effectiveperlprogramming.com/blog/1271 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 Newnham reopened JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin Reopening. Change By: Alex Newnham (26/Nov/12 11:17 AM) Resolution: Not A Defect Status: Resolved Reopened 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 Newnham commented on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin Thanks for the update We are parsing our .t files via TAP::Harness using Test::Harness v3.25 which states it's output is TAP version 12. Perhaps there's a mismatch here somewhere between the TAP produced by our Test::More module and Tap::Harness and the TAP specifications. Or maybe the plugin is expecting a different TAP version? Currently I can't investigate further as http://testanything.org is down at the moment. In our projects we can't easily switch to using prove from the command line or a bash script as our .t files aren't static, they rely on a whole bunch of variable being passed into them via the TAP::Harness, there may be other workarounds possible though. 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
Bruno P. Kinoshita reopened JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin Change By: Bruno P. Kinoshita (25/Nov/12 2:58 AM) Resolution: Fixed Status: Resolved Reopened 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
Bruno P. Kinoshita resolved JENKINS-15322 as Not A Defect NOTESTS in TAP response gives parse error and stack trace from plugin Change By: Bruno P. Kinoshita (25/Nov/12 2:58 AM) Status: Reopened Resolved Resolution: Not A Defect 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
Bruno P. Kinoshita commented on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin Sorry, I sent the code to the wrong issue. Ignore the comment above. This issue is being marked as not a defect (not as fixed) while we discuss about prove/tap. 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
SCM/JIRA link daemon resolved JENKINS-15322 as Fixed NOTESTS in TAP response gives parse error and stack trace from plugin Change By: SCM/JIRA link daemon (25/Nov/12 2:52 AM) Status: Open Resolved Resolution: Fixed 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
SCM/JIRA link daemon commented on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin Code changed in jenkins User: Bruno P. Kinoshita Path: pom.xml src/main/java/org/tap4j/plugin/TapParser.java src/main/java/org/tap4j/plugin/TapPublisher.java src/main/java/org/tap4j/plugin/model/TapTestResultResult.java src/main/resources/org/tap4j/plugin/TapPublisher/config.jelly http://jenkins-ci.org/commit/tap-plugin/ae773491476f022cf11afbe7c820b76b36bbb646 Log: [FIXED JENKINS-15322] Fixed bug after a new release in tap4j. The parser was treating unknown content as subtests 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
Bruno P. Kinoshita commented on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin 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 No tests run! 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 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
Bruno P. Kinoshita stopped work on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin Change By: Bruno P. Kinoshita (24/Nov/12 11:00 PM) Status: In Progress Open 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 Newnham commented on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin Hi Bruno, here's another NOTESTS .tap file, generated from skip_all as detailed in http://search.cpan.org/~mschwern/Test-Simple-0.98/lib/Test/More.pm We also supplied a $skip_reason (specifically " No Relevant Tests as No DB Costs for RequestConfig2V11EncoreNew"). /opt/performance/scripts/t/dbcoststest1.t .. skipped: No Relevant Tests as No DB Costs for RequestConfig2V11EncoreNew Files=1, Tests=0, 1 wallclock secs ( 0.00 usr 0.01 sys + 0.55 cusr 0.06 csys = 0.62 CPU) Result: NOTESTS 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
Bruno P. Kinoshita commented on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin Hi Alex, I'm not familiar with NOTESTS. Could you provide an example TAP Stream, please? Would it be something like: somefile.tap 1..0 ? 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
Bruno P. Kinoshita started work on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin Change By: Bruno P. Kinoshita (12/Oct/12 7:35 PM) Status: Open In Progress 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 Newnham commented on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin One course of action would be to mark the file as skipped with no associated FAIL, given that No Tests are being explicitly requested. 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 Newnham created JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin Issue Type: Bug Affects Versions: current Assignee: Bruno P. Kinoshita Components: tap Created: 26/Sep/12 4:34 PM Description: A .tap file containing a NOTESTS result (from eg a skip_all declaration in a .t file) such as /opt/performance/scripts/t/dbcoststest1.t .. skipped: No Relevant Tests as No DB Costs for GetSmoidTrackV11New Files=1, Tests=0, 1 wallclock secs ( 0.01 usr 0.02 sys + 0.54 cusr 0.04 csys = 0.61 CPU) Result: NOTESTS results in the following errors when running a plan from Jenkins: Parsing TAP test result [/var/lib/jenkins/jobs/Performance-Server-Trunk/builds/2012-09-26_16-06-21/tap/dbcostsGetSmoidTrackV11New.tap]. org.tap4j.parser.ParserException: Error parsing TAP Stream: Missing TAP Plan. at org.tap4j.parser.Tap13YamlParser.parseFile(Tap13YamlParser.java:587) at org.tap4j.plugin.TapParser.parse(TapParser.java:94) at org.tap4j.plugin.TapPublisher.loadResults(TapPublisher.java:240) at org.tap4j.plugin.TapPublisher.perform(TapPublisher.java:182) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:27) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:705) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:680) at hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.java:996) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:627) at hudson.model.Run.run(Run.java:1438) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:479) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Caused by: org.tap4j.parser.ParserException: Missing TAP Plan. at org.tap4j.parser.Tap13YamlParser.checkTAPPlanIsSet(Tap13YamlParser.java:353) at org.tap4j.parser.Tap13YamlParser.postProcess(Tap13YamlParser.java:736) at org.tap4j.parser.Tap13YamlParser.parseFile(Tap13YamlParser.java:585) ... 12 more Environment: centos 6 Project: Jenkins Labels: tap Priority: Major Reporter: Alex Newnham 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
