[
https://issues.apache.org/jira/browse/YETUS-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14986164#comment-14986164
]
Andrew Wang commented on YETUS-146:
-----------------------------------
Not sure I follow the concerns here, please bear with me:
bq. 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...
So the links I see are to the captured stdout of calling mvn test, it doesn't
seem specific to failed tests unless you mean the presence of this table line
at all is because some tests failed.
bq. 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 think this is the behavior I'm asking for. If the top-level script already
links the full stdout of each plugin (I think this is the "unit test logs"
row?), I don't see why the plugin also needs to link it. Should be no reduction
in information?
> 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)
