[
https://issues.apache.org/jira/browse/HADOOP-11549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14305844#comment-14305844
]
Yongjun Zhang commented on HADOOP-11549:
----------------------------------------
Hi [~ozawa] and [~ajisakaa],
Thank you guys for the help with HADOOP-11045 earlier.
I was testing the hadoop-common side earlier, and tried hdfs today and saw this
problem. I found a solution here and tested it against python 2.x and 3.x.
Another side problem I observed is what Akira pointed out in earlier review
about permission bits. I did set the permission bits per Akira's comments. When
I synced in the latest trunk, I saw that the tool script doesn't have exe
permission.
Let's see if my patch here can address both issues.
Thanks a lot for following up.
> 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
> Affects Versions: 2.7.0
> Reporter: Yongjun Zhang
> Assignee: Yongjun Zhang
> Attachments: HADOOP-11549.001.patch
>
>
> 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)
