[ 
https://issues.apache.org/jira/browse/HADOOP-11551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14310304#comment-14310304
 ] 

Yongjun Zhang commented on HADOOP-11551:
----------------------------------------

HI [~ozawa],

Thanks, very good comment!

I think ideally if we can put a link in the summary page of a job, right below 
the "Test Result" section ("Test Result" itself is a link).

E.g. https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2047/

{code}
......
Test Result (2 failures / ±0)
org.apache.hadoop.mapred.TestMRTimelineEventHandling.testMapreduceJobTimelineServiceEnabled

Flaky Test Detection Result  (link to flaky test detection result, addition as 
a result of fixing this jira)
{code}

But I'm not sure how convenient to add it.

A simpler way is to make the result part of the console output, e.g., at the 
bottom of 
https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2047/console

What do you think?

Thanks.


> Let nightly jenkins jobs run the tool of HADOOP-11045 and include the result 
> in the job report
> ----------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-11551
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11551
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: build, tools
>            Reporter: Yongjun Zhang
>            Assignee: Yongjun Zhang
>
> This jira is to propose running the tool created with HADOOP-11045 at the end 
> of jenkins test job - I am thinking about trunk jobs currently - and report 
> the results at the job report. This way when we look at test failure, we can 
> tell the failure pattern, and whether failed test is likely a flaky test or 
> not.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to