http://jenkins.cloudstack.org/view/master/job/build-master-nonoss-rhel63/
Yes, it is started breaking from build # 34. http://jenkins.cloudstack.org/view/master/job/build-master-nonoss-rhel63/34/console Till 33, it went fine... Thanks, Pradeep S -----Original Message----- From: Min Chen [mailto:min.c...@citrix.com] Sent: Friday, January 18, 2013 11:19 AM To: cloudstack-dev@incubator.apache.org Subject: Re: [MERGE] network refactoring, phase 1 Nonoss build is broken in master branch, not sure if it is related to this merge? [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile) on project cloud-plugin-network-f5: Compilation failure [ERROR] /Users/minc/dev/cloud-asf/plugins/network-elements/f5/src/com/cloud/network /element/F5ExternalLoadBalancerElement.java:[499,27] cannot find symbol [ERROR] symbol : method isNetworkInlineMode(com.cloud.network.Network) [ERROR] location: interface com.cloud.network.NetworkModel [ERROR] -> [Help 1] Thanks -min On 1/17/13 5:15 PM, "Chiradeep Vittal" <chiradeep.vit...@citrix.com> wrote: >Merge done. Tool issue. > >On 1/16/13 11:21 PM, "Chiradeep Vittal" <chiradeep.vit...@citrix.com> >wrote: > >>Having problems with the merge. ETA is Thursday evening PST. >> >>On 1/16/13 3:40 PM, "Chiradeep Vittal" <chiradeep.vit...@citrix.com> >>wrote: >> >>>OK , will re-do the merge and re-test and commit by EOD >>> >>>On 1/16/13 1:56 PM, "Animesh Chaturvedi" >>><animesh.chaturv...@citrix.com> >>>wrote: >>> >>>>Chiradeep >>>> >>>>Are you waiting on revert for 312? Murali reverted it today >>>> >>>>Thanks >>>>Animesh >>>> >>>>> -----Original Message----- >>>>> From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com] >>>>> Sent: Friday, January 11, 2013 1:08 PM >>>>> To: CloudStack DeveloperList >>>>> Subject: Re: [MERGE] network refactoring, phase 1 >>>>> >>>>> I'm going to wait on the reverts for CLOUDSTACK-306 and >>>>>CLOUDSTACK-312 >>>>> >>>>> On 1/11/13 12:15 PM, "Alex Huang" <alex.hu...@citrix.com> wrote: >>>>> >>>>> >> +1 - with an assumption that Alex and others are OK with it >>>>> >> +(since >>>>>the >>>>> >> javelin branch merge was proposed first). >>>>> > >>>>> >+1 We're struggling with the merge right now so one more merge is >>>>>not >>>>> >going to hurt very much. >>>>> > >>>>> >--Alex >>>> >>> >> >
