[jira] [Commented] (HDFS-8063) Fix test failure in TestTracing

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

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

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12709468/HDFS-8063.001.patch
  against trunk revision 96d7211.

    {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:green}+1 core tests{color}.  The patch passed unit tests in hadoop-hdfs-project/hadoop-hdfs.

Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/10180//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/10180//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
>
>
> 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)