[
https://issues.apache.org/jira/browse/YETUS-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14986131#comment-14986131
]
Allen Wittenauer commented on YETUS-146:
----------------------------------------
bq. Also the one about the failed tests table pointing at the wrong JDK. Should
I file a separate JIRA for that?
Already filed and fixed (YETUS-147).
bq. Do we agree though that the original issue exists though, about the 3 table
lines with the same two links twice? This isn't seem dependent on Jenkins vs
local execution.
One is a link to all of the unit tests, regardless of outcome. The other is a
link generated by the junit plug-in that points to its specific results that it
flagged as bad. (TAP, on the other hand, will link to the specific log for the
specific test.)
* does junit link to just the failed tests? what if another test format (like
TAP) actually wants to list both? Then junit and TAP might link to the same
log entry anyway...
* does the unit test driver just not list any logs? but what if there is a
problem that occurred outside the test that then failed the actual junit or TAP
result?
I'm not sure one would be able to answer all questions during a failure without
providing some excessive log coverage here. This is especially true if the goal
is to avoid people from having to traipse through the patch processing
directory where all this stuff is dumped.
> Duplicate links to unit test logs
> ---------------------------------
>
> Key: YETUS-146
> URL: https://issues.apache.org/jira/browse/YETUS-146
> Project: Yetus
> Issue Type: Improvement
> Reporter: Andrew Wang
>
> Saw a run on HDFS-9332 where we get three table lines. The first two contain
> links to test logs for each JDK run, and the third contains the same links
> again. Seems duplicate.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
