hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Allen Wittenauer ...@altiscale.com>
Subject Re: Uncertainty of pre-commit builds
Date Tue, 31 Mar 2015 16:37:58 GMT

	Very likely.  One of the things I noticed during HADOOP-11746 is that there is a HUGE, catastrophic
race if Jenkins doesn’t setup the environment correctly or leaks variables between runs.
 shellcheck prints out so many messages on the current code I’m surprised it doesn’t crash.

On Mar 31, 2015, at 9:21 AM, Karthik Kambatla <kasha@cloudera.com> wrote:

> Hi devs,
> I am sure people must have noticed, but thought I would bring this up.
> I have noticed that our pre-commit builds could end up running the "wrong"
> set of unit tests for patches. For instance, YARN-3412
> <https://issues.apache.org/jira/browse/YARN-3412> changes only YARN files,
> but the test were run against one of the MR modules.
> I suspect there is a race condition when there are multiple builds
> executing on the same node, or remnants from a previous run are getting
> picked up.
> Filed HADOOP-11779 for this.
> -- 
> Karthik Kambatla
> Software Engineer, Cloudera Inc.
> --------------------------------------------
> http://five.sentenc.es

View raw message