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

Hadoop QA commented on HDFS-8063:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12724063/HDFS-8063.002.patch
  against trunk revision cc25823.

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in 
hadoop-hdfs-project/hadoop-hdfs:

                  
org.apache.hadoop.hdfs.server.namenode.TestNameNodeResourceChecker

Test results: 
https://builds.apache.org/job/PreCommit-HDFS-Build/10219//testReport/
Console output: 
https://builds.apache.org/job/PreCommit-HDFS-Build/10219//console

This message is automatically generated.

> Fix test failure in TestTracing
> -------------------------------
>
>                 Key: HDFS-8063
>                 URL: https://issues.apache.org/jira/browse/HDFS-8063
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: test
>            Reporter: Masatake Iwasaki
>            Assignee: Masatake Iwasaki
>            Priority: Minor
>         Attachments: HDFS-8063.001.patch, HDFS-8063.002.patch, 
> testReadTraceHooks.html
>
>
> Tests in TestTracing sometimes fails, especially on slow machine. The cause 
> is that spans is possible to arrive at receiver after 
> {{assertSpanNamesFound}} passed and 
> {{SetSpanReceiver.SetHolder.spans.clear()}} is called for next test case.



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

Reply via email to