[
https://issues.apache.org/jira/browse/HADOOP-11551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14308723#comment-14308723
]
Tsuyoshi OZAWA commented on HADOOP-11551:
-----------------------------------------
{code}
For pre-commit test, the result would be not consistent because it involves
uncommitted patches. I was thinking about adding it only for committed code,
the nightly jobs run on trunk.
{code}
Make sense. One question: if we add it for committed code, where should we
print the lists of flaky tests?
> 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)
