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 <t...@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.
