-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
jenkins 1.584, tap-plugin 1.23
Diagnostic lines, in the source TAP file, look like
not ok 3 foo.lux # FAIL at line 13:34 # expected # ==0== # actual fail pattern matched "==1=="
but when checking the TAP results in the Jenkins UI (tap-plugin views), it comes out as
# FAIL at line 13:34 # expected # ==0== # actual fail pattern matched "==1=="
The same happens with whitespaces after the # sign, which is even worse (think pretty-printed JSON output).
Interesting. I wonder if there was a regression, but I couldn't get the plugin view to display the comments.
1. Used the following TAP stream
But going to TAP Extended Test Results always displays only the test results, without the comments. Clicked on advanced, and checked the option to display comments, but nothing.
Any idea what I'm missing here?