> accidentally separated two scripts that had to stay together. My fault, I had no idea this kind of coupling existed. Adding comments [1] to prevent similar errors in future.
Vratko. [1] https://gerrit.fd.io/r/c/ci-management/+/24348 From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of Christian Hopps Sent: Wednesday, January 15, 2020 1:10 AM To: Ed Kern (ejk) <e...@cisco.com> Cc: Christian Hopps <cho...@chopps.org>; Andrew 👽 Yourtchenko <ayour...@gmail.com>; Florin Coras <fcoras.li...@gmail.com>; vpp-dev <vpp-dev@lists.fd.io> Subject: Re: [vpp-dev] Arm verify job broken > On Jan 14, 2020, at 6:27 PM, Ed Kern via Lists.Fd.Io > <ejk=cisco....@lists.fd.io<mailto:ejk=cisco....@lists.fd.io>> wrote: > > short answer: fixed.. > > > longer answer: a ci-management patch which did a whole bunch of cleanup and > readability improvements accidentally > separated two scripts that had to stay together. Having the script apart > meant arm was using only 1 core instead > of the correct number of 16 cores. > > This lead to all arm jobs answering the question ‘what does a yellow light > mean’ (apologies to those that miss the taxi reference) Now that's a blast from the past... :) Thanks, Chris. > > ci-man patch being merged now…all subsequent jobs should be back to normal > timing. > > Ed > > > >> On Jan 14, 2020, at 1:54 PM, Andrew 👽 Yourtchenko >> <ayour...@gmail.com<mailto:ayour...@gmail.com>> wrote: >> >> better to debug some before changing anything. >> >> With my RM hat on I would rather understand what is going on, if it is 24 >> hours before the RC1 milestone ;-) >> >> --a >> >>> On 14 Jan 2020, at 21:28, Ed Kern via Lists.Fd.Io >>> <ejk=cisco....@lists.fd.io<mailto:ejk=cisco....@lists.fd.io>> wrote: >>> >>>  ok FOR THE MOST PART… build times haven’t changed (@20 min) >>> >>> make test portion has gone off the chain and is often hitting the 120 min >>> build timeout threshold. >>> >>> Ive currently got several jobs running on sandbox testing >>> >>> a. without any timeouts (just to see if we are still passing on master) >>> b. three different memory and disk profiles (just in case someone/thing got >>> messy and we have had another memory spike) >>> >>> the bad news is that it will be at least a couple of hours more than likely >>> before I get any results that I feel are actionable. >>> >>> >>> Having said that im happy to shoot the build timeout for the time being if >>> committers feel that is warranted to ‘keep the train rolling’ >>> >>> Ed >>> >>> >>> >>> >>>> On Jan 14, 2020, at 1:07 PM, Florin Coras >>>> <fcoras.li...@gmail.com<mailto:fcoras.li...@gmail.com>> wrote: >>>> >>>> Thanks, Ed! >>>> >>>> Florin >>>> >>>>> On Jan 14, 2020, at 11:53 AM, Ed Kern (ejk) >>>>> <e...@cisco.com<mailto:e...@cisco.com>> wrote: >>>>> >>>>> looking into it now….. >>>>> >>>>> its a strange one ill tell you that up front…failures are all over the >>>>> place inside the build and even some hitting the 120 min timeout…. >>>>> >>>>> more as i dig hopefully >>>>> >>>>> thanks for the ping >>>>> >>>>> Ed >>>>> >>>>> >>>>> >>>>>> On Jan 14, 2020, at 11:40 AM, Florin Coras >>>>>> <fcoras.li...@gmail.com<mailto:fcoras.li...@gmail.com>> wrote: >>>>>> >>>>>> Hi, >>>>>> >>>>>> Jobs have been failing since yesterday. Did anybody try to look into it? >>>>>> >>>>>> Regards, >>>>>> Florin >>>>>> >>>>> >>>> >>> >>> > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#15181): https://lists.fd.io/g/vpp-dev/message/15181 Mute This Topic: https://lists.fd.io/mt/69698855/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
