[ https://issues.apache.org/jira/browse/HADOOP-11549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14307304#comment-14307304 ]
Hudson commented on HADOOP-11549: --------------------------------- SUCCESS: Integrated in Hadoop-Hdfs-trunk-Java8 #92 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/92/]) HADOOP-11549. flaky test detection tool failed to handle special control characters in test result. Contributed by Yongjun Zhang. (aajisaka: rev 5f4ef2d13fa3fa3d4d315902e55c7775ef08b3d2) * hadoop-common-project/hadoop-common/CHANGES.txt * dev-support/determine-flaky-tests-hadoop.py > 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 > Fix For: 2.7.0 > > 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)