cc-ing the release list in case other devs are experiencing similar problems with their builds.
> On Dec 15, 2017, at 11:31 AM, Thanh Ha <[email protected]> wrote: > > Alright I talked to Andy and we're gonna bump all the java-builders to the > v1-performance-2 machines. This should (hopefully) make those jobs pass more > quickly. > > Regards, > Thanh > > On Fri, Dec 15, 2017 at 2:18 PM, Thanh Ha <[email protected] > <mailto:[email protected]>> wrote: > Let me think about this a bit. I think the slowness is because in the new > cloud we went from 2 CPUs (old) to 1 CPU (new). The new provider provides the > following flavors for us: > > v1-performance-1: 1 cpu & 4 gb ram > v1-performance-2: 2 cpu & 8 gb ram > v1-performance-4: 4 cpu & 16 gb ram > v1-performance-8: 8 cpu & 32 gb ram > > So to get the performance back to where we were in the old cloud we should be > using performance-2 nodes instead but that means our builders will now > default to 8 gb builders which I'm not sure we want to do right now. > > I've asked the cloud provider if we can get a 2 cpu & 4 gb ram flavor and > will ask internally if going with the performance-2 right is something we > want to take a hit on. > > Regards, > Thanh > > On Fri, Dec 15, 2017 at 1:41 PM, Tom Pantelis <[email protected] > <mailto:[email protected]>> wrote: > Sorry I though an individual SFT took an hour but I think Luis is right - > it's the overall build time: > > 17:49:31 Running org.opendaylight.odlparent.featuretest.SingleFeatureTest > 17:50:12 Build timed out (after 60 minutes). Marking the build as failed. > > This is happening in several projects (at least). Thanh - I assume there's a > default setting - if so, can you increase it to like 2 hrs? I'm hoping it > doesn't need to be set per project. > > On Fri, Dec 15, 2017 at 12:39 PM, Thanh Ha <[email protected] > <mailto:[email protected]>> wrote: > All of our maven-* jobs have a "build-timeout" parameter that let's you > override. Just add it to the project.yaml file. Here's an example in releng: > > https://github.com/opendaylight/releng-builder/blob/master/jjb/releng-jobs.yaml#L25 > > <https://github.com/opendaylight/releng-builder/blob/master/jjb/releng-jobs.yaml#L25> > > Regards, > Thanh > > > On Fri, Dec 15, 2017 at 12:10 PM, Luis Gomez <[email protected] > <mailto:[email protected]>> wrote: > I suspect the reason is: > > Build timed out (after 60 minutes). Marking the build as failed. > > I believe some projects in ODL take ~1 hour to build and probably more after > the cloud migration. Thanh, do you know where to change this timeout? > > BR/Luis > > >> On Dec 15, 2017, at 5:49 AM, Tom Pantelis <[email protected] >> <mailto:[email protected]>> wrote: >> >> Hello, >> >> I pushed patches to do the bump and fix build errors: >> >> https://git.opendaylight.org/gerrit/#/c/66493/ >> <https://git.opendaylight.org/gerrit/#/c/66493/> - Fix odlparent 3 >> Checkstyle issues >> https://git.opendaylight.org/gerrit/#/c/66494/ >> <https://git.opendaylight.org/gerrit/#/c/66494/> - Bump to yangtools-2.0.0 >> and odlparent-3.0.2 >> >> The first one should build but got an SFT timeout - don't know why - passes >> locally for me. >> >> Not sure who all the active committers are now but I'll leave it in your >> hands now. >> >> Anil - I tried to add you as reviewer but it said it didn't recognize you. >> It would seem your account is disabled after the gerrit migration... >> >> Tom >> _______________________________________________ >> openflowplugin-dev mailing list >> [email protected] >> <mailto:[email protected]> >> https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev >> <https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev> > > > > >
_______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
