hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HADOOP-11746) rewrite test-patch.sh
Date Wed, 22 Apr 2015 07:30:01 GMT

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

Allen Wittenauer edited comment on HADOOP-11746 at 4/22/15 7:29 AM:
--------------------------------------------------------------------

I posted this on -dev, but to copy the status update here:

* So far, HADOOP-11861 was filed which is luckily an extremely easy bug to fix.

* There have been a few runs which seems to indicate that *something* is destroying the artifact
directory in the middle of runs…. which is very very odd and something I hadn’t seen in
any of my testing.  In any case, I clearly need to add some safety code here to report back
that something went awry and report back which node, console, etc this happened on. Someone
more familiar with the Jenkins setup might be able to shed some light on why that might happen.
All of these runs appear to be on H3, so might be related? Impacted issues with this have
been:

- HDFS-8200 (https://builds.apache.org/job/PreCommit-HDFS-Build/10335/)
- HDFS-8147 (https://builds.apache.org/job/PreCommit-HDFS-Build/10338/)
- YARN-3301 (https://builds.apache.org/job/PreCommit-YARN-Build/7441/) 

* Some sort of good news! The new mvn site test does appear to be capable of catching issues!
 YARN-3410 was committed just prior to the new test code and has markdown-to-html syntax issues.
 HADOOP-11627 (for example) shows the results. :D


was (Author: aw):
I posted this on -dev, but to copy the status update here:

* So far, HADOOP-11627 was filed which is luckily an extremely easy bug to fix.

* There have been a few runs which seems to indicate that *something* is destroying the artifact
directory in the middle of runs…. which is very very odd and something I hadn’t seen in
any of my testing.  In any case, I clearly need to add some safety code here to report back
that something went awry and report back which node, console, etc this happened on. Someone
more familiar with the Jenkins setup might be able to shed some light on why that might happen.
All of these runs appear to be on H3, so might be related? Impacted issues with this have
been:

- HDFS-8200 (https://builds.apache.org/job/PreCommit-HDFS-Build/10335/)
- HDFS-8147 (https://builds.apache.org/job/PreCommit-HDFS-Build/10338/)
- YARN-3301 (https://builds.apache.org/job/PreCommit-YARN-Build/7441/) 

* Some sort of good news! The new mvn site test does appear to be capable of catching issues!
 YARN-3410 was committed just prior to the new test code and has markdown-to-html syntax issues.
 HADOOP-11627 (for example) shows the results. :D

> rewrite test-patch.sh
> ---------------------
>
>                 Key: HADOOP-11746
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11746
>             Project: Hadoop Common
>          Issue Type: Test
>          Components: build, test
>    Affects Versions: 3.0.0
>            Reporter: Allen Wittenauer
>            Assignee: Allen Wittenauer
>             Fix For: 2.8.0
>
>         Attachments: HADOOP-11746-00.patch, HADOOP-11746-01.patch, HADOOP-11746-02.patch,
HADOOP-11746-03.patch, HADOOP-11746-04.patch, HADOOP-11746-05.patch, HADOOP-11746-06.patch,
HADOOP-11746-07.patch, HADOOP-11746-09.patch, HADOOP-11746-10.patch, HADOOP-11746-11.patch,
HADOOP-11746-12.patch, HADOOP-11746-13.patch, HADOOP-11746-14.patch, HADOOP-11746-15.patch,
HADOOP-11746-16.patch, HADOOP-11746-17.patch, HADOOP-11746-18.patch, HADOOP-11746-19.patch,
HADOOP-11746-20.patch, HADOOP-11746-21.branch-2.patch, HADOOP-11746-21.patch
>
>
> This code is bad and you should feel bad.



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

Mime
View raw message