Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Received-SPF: pass (athena.apache.org: domain of yzhang@cloudera.com
 designates 209.85.192.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <437381758.227501.1423158571738.JavaMail.yahoo@mail.yahoo.com>
References: <437381758.227501.1423158571738.JavaMail.yahoo@mail.yahoo.com>
Date: Thu, 5 Feb 2015 10:42:01 -0800
Message-ID: 
 <CAA0W1bSrZNK-eN=qKtvcG0yHPV_DF4JXTzey=9EXsiu3wLLuPA@mail.gmail.com>
Subject: Re: Erratic Jenkins behavior
From: Yongjun Zhang <yzhang@cloudera.com>
To: common-dev@hadoop.apache.org, Kihwal Lee <kihwal@yahoo-inc.com>
Cc: "hdfs-dev@hadoop.apache.org" <hdfs-dev@hadoop.apache.org>,
	"yarn-dev@hadoop.apache.org" <yarn-dev@hadoop.apache.org>
Content-Type: multipart/alternative; boundary=001a11397ec0d95269050e5ba891

--001a11397ec0d95269050e5ba891
Content-Type: text/plain; charset=UTF-8

Thanks Kihwal for bringing this up.

Seems related to:

https://issues.apache.org/jira/browse/HADOOP-11084

Hi Andrew/Arpit/Colin/Steve, you guys worked on this jira before, any
insight about the issue Kihwal described?

Thanks.

--Yongjun


On Thu, Feb 5, 2015 at 9:49 AM, Kihwal Lee <kihwal@yahoo-inc.com.invalid>
wrote:

> I am sure many of us have seen strange jenkins behavior out of the
> precommit builds.
>
> - build artifacts missing
> - serving build artifact belonging to another build. This also causes
> wrong precommit results to be posted on the bug.
> - etc.
>
> The latest one I saw is disappearance of the unit test stdout/stderr file
> during a build. After a successful run of unit tests, the file vanished, so
> the script could not cat it. It looked like another build process had
> deleted it, while this build was in progress.
>
> It might have something to do with the fact that the patch-dir is set like
> following:
>
> PATCHPROCESS=/home/jenkins/jenkins-slave/workspace/PreCommit-HDFS-Build/../patchprocessI
> don't have access to the jenkins build configs or the build machines, so I
> can't debug it further, but I think we need to take care of it sooner than
> later.  Can any one help?
>
> Kihwal
>

--001a11397ec0d95269050e5ba891--