You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by prasanna <ts...@apache.org> on 2013/03/01 06:04:50 UTC
4.1 build broken?
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.
Re: 4.1 build broken?
Posted by prasanna <sr...@gmail.com>.
Just fixed it 3afc226
On 1 March 2013 11:19, Marcus Sorensen <sh...@gmail.com> wrote:
> Ok. I'm just taking a quick second to see if I can figure out what is
> causing the problem, but I'll get it back on asap.
>
> On Thu, Feb 28, 2013 at 10:46 PM, David Nalley <da...@gnsa.us> wrote:
>> On Fri, Mar 1, 2013 at 12:37 AM, Marcus Sorensen <sh...@gmail.com> wrote:
>>> 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?
>>>
>>
>>
>> Marcus:
>>
>> Revert it - get us back to a buildable state.
>>
>> --David
--
Prasanna.,
Re: 4.1 build broken?
Posted by Marcus Sorensen <sh...@gmail.com>.
Ok. I'm just taking a quick second to see if I can figure out what is
causing the problem, but I'll get it back on asap.
On Thu, Feb 28, 2013 at 10:46 PM, David Nalley <da...@gnsa.us> wrote:
> On Fri, Mar 1, 2013 at 12:37 AM, Marcus Sorensen <sh...@gmail.com> wrote:
>> 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?
>>
>
>
> Marcus:
>
> Revert it - get us back to a buildable state.
>
> --David
Re: 4.1 build broken?
Posted by David Nalley <da...@gnsa.us>.
On Fri, Mar 1, 2013 at 12:37 AM, Marcus Sorensen <sh...@gmail.com> wrote:
> 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?
>
Marcus:
Revert it - get us back to a buildable state.
--David
Re: 4.1 build broken?
Posted by Marcus Sorensen <sh...@gmail.com>.
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 <ts...@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.