hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yongjun Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-11549) flaky test detection tool failed to handle special control characters in test result
Date Wed, 04 Feb 2015 19:48:34 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-11549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Yongjun Zhang updated HADOOP-11549:
-----------------------------------
    Description: 
When running the tool from HADOOP-11045 on latest Hadoop-hdfs-trunk job, I'm seeing a problem
here:

{code}
[yzhang@localhost jenkinsftf]$ ./determine-flaky-tests-hadoop.py -j Hadoop-hdfs-trunk 
****Recently FAILED builds in url: https://builds.apache.org/job/Hadoop-hdfs-trunk
    THERE ARE 5 builds (out of 6) that have failed tests in the past 14 days, as listed below:

===>https://builds.apache.org/job/Hadoop-hdfs-trunk/2026/testReport (2015-02-04 03:30:00)
    Could not open testReport, check https://builds.apache.org/job/Hadoop-hdfs-trunk/2026/Console
for why it was reported failed
...
{code}

I saw that the testReport can actually be opened from browser. After looking, I found that
HDFS-7287 fix added the following test code:
{code}
//Create a directory whose name should be escaped in XML
Path invalidXMLDir = new Path("/dirContainingInvalidXMLChar\u0000here");
hdfs.mkdirs(invalidXMLDir);
...
{code}
And the output from this code caused the tool to choke. 

I found a solution here and I'm attaching a patch.
 

  was:
When running the tool from HADOOP-11045 on latest Hadoop-hdfs-trunk job, I'm seeing a problem
here:

{code}
[yzhang@localhost jenkinsftf]$ ./determine-flaky-tests-hadoop.py -j Hadoop-hdfs-trunk 
****Recently FAILED builds in url: https://builds.apache.org/job/Hadoop-hdfs-trunk
    THERE ARE 5 builds (out of 6) that have failed tests in the past 14 days, as listed below:

===>https://builds.apache.org/job/Hadoop-hdfs-trunk/2026/testReport (2015-02-04 03:30:00)
    Could not open testReport, check https://builds.apache.org/job/Hadoop-hdfs-trunk/2026/Console
for why it was reported failed
...
{code}

After looking, I found that HDFS-7287 fix added the following test code:
{code}
//Create a directory whose name should be escaped in XML
Path invalidXMLDir = new Path("/dirContainingInvalidXMLChar\u0000here");
hdfs.mkdirs(invalidXMLDir);
...
{code}
And the output from this code caused the tool to choke. 

I found a solution here and I'm attaching a patch.
 


> flaky test detection tool failed to handle special control characters in test result
> ------------------------------------------------------------------------------------
>
>                 Key: HADOOP-11549
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11549
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: tools
>            Reporter: Yongjun Zhang
>            Assignee: Yongjun Zhang
>
> When running the tool from HADOOP-11045 on latest Hadoop-hdfs-trunk job, I'm seeing a
problem here:
> {code}
> [yzhang@localhost jenkinsftf]$ ./determine-flaky-tests-hadoop.py -j Hadoop-hdfs-trunk

> ****Recently FAILED builds in url: https://builds.apache.org/job/Hadoop-hdfs-trunk
>     THERE ARE 5 builds (out of 6) that have failed tests in the past 14 days, as listed
below:
> ===>https://builds.apache.org/job/Hadoop-hdfs-trunk/2026/testReport (2015-02-04 03:30:00)
>     Could not open testReport, check https://builds.apache.org/job/Hadoop-hdfs-trunk/2026/Console
for why it was reported failed
> ...
> {code}
> I saw that the testReport can actually be opened from browser. After looking, I found
that HDFS-7287 fix added the following test code:
> {code}
> //Create a directory whose name should be escaped in XML
> Path invalidXMLDir = new Path("/dirContainingInvalidXMLChar\u0000here");
> hdfs.mkdirs(invalidXMLDir);
> ...
> {code}
> And the output from this code caused the tool to choke. 
> I found a solution here and I'm attaching a patch.
>  



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

Mime
View raw message