-
Bug
-
Resolution: Not A Defect
-
Major
-
None
In perl test suites, it's common to do a SKIPALL on certain test files when you for instance determine that you're on the wrong OS, or if long tests are not enabled.
<testsuites> <testsuite failures="0" errors="0" tests="0" name="00_devel_smoke_binaries_t"> <system-out><![CDATA[1..0 # SKIP Long-running tests disabled unless SLOW_TESTS environment variable set. ]]></system-out> <system-err></system-err> </testsuite> </testsuites>
When the TAP parser hits these, it declares the build a failure. If the well formed XML is declaring 0 tests, how is this a failure condition?
[JENKINS-16326] TAP Parser can't handle SKIP_ALL
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Attachment | New: screenshot004.png [ 23238 ] | |
Attachment | New: screenshot005.png [ 23239 ] |
Attachment | New: screenshot006.png [ 23240 ] |
Status | Original: In Progress [ 3 ] | New: Open [ 1 ] |
Resolution | New: Not A Defect [ 7 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JNJira [ 147141 ] | New: JNJira + In-Review [ 206326 ] |