Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of shadowsor@gmail.com designates
 209.85.220.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAEwhOu+0hn72akz9zxLahNTuME+Lq=viq5d_nrb0oUi6T5qTjg@mail.gmail.com>
References: 
 <CAEwhOu+0hn72akz9zxLahNTuME+Lq=viq5d_nrb0oUi6T5qTjg@mail.gmail.com>
Date: Thu, 28 Feb 2013 22:37:37 -0700
Message-ID: 
 <CALFpzo7e7t_dOEOhwEFf7eM6sCs7hm9TimB+9Dx6uEWtFQaJNQ@mail.gmail.com>
Subject: Re: 4.1 build broken?
From: Marcus Sorensen <shadowsor@gmail.com>
To: cloudstack-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Looks like it's this one: 13ec069129bf46ffd327d52cf26f5fc363a13284, if
I go back to the commit prior to that it builds. I reverted that on my
local git and it built fine.

Come on guys, this is happening entirely too often. I can understand
when a commit has some unexpected side effect in the running code, but
how hard is it to make sure your code compiles before pushing it? I
hate to be that guy, but whenever this happens how many people does it
block?

On Thu, Feb 28, 2013 at 10:04 PM, prasanna <tsp@apache.org> wrote:
> Looks like the 4.1 build is broken? Anyone looking at it?
> http://jenkins.cloudstack.org/job/build-4.1/206/changes
>
> It takes a while for the email to come from the apache jenkins since
> the job gets queued amidst tons of others there.