From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-ua1-f50.google.com (mail-ua1-f50.google.com [209.85.222.50]) by mx.groups.io with SMTP id smtpd.web12.25079.1640207949787540892 for ; Wed, 22 Dec 2021 13:19:09 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20210112 header.b=RB/TpDtC; spf=pass (domain: gmail.com, ip: 209.85.222.50, mailfrom: pedro.falcato@gmail.com) Received: by mail-ua1-f50.google.com with SMTP id 30so6394711uag.13 for ; Wed, 22 Dec 2021 13:19:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=J/BzibAHpq4HtTRGDTXoTPoGMIXBpIe4p1WBwFKCDmE=; b=RB/TpDtCCpjoSGyyC19E/jw2ENh5LCFH+3Uu/UYcoGag0lBwRDEdZOv+GQpNxWXUx6 GTPI6+XnMfiJSBA1mdhMG+rfj0dvFCp2vNEeGRHUaERvfoC4uRbCrxlIY01VySZgAe4b ySFpahIozO3fchNZJHNYuiIGlY/w3oGz7IDQQrLpyhOd2aXIRX+urZUcy3wFYQyBPrro DQYC7Amm58XSHYPGJcWrTRJH0MfX/FFoTCOHKFGIl/cYvriHaB7iDX3psefwo+WRj7nu Q5KPb5Da5407yu9wFwi7rGtVnHXR77QcsA5LCLlIrCbayAolssVeCDBgBW/6KvxVBv8j giBg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=J/BzibAHpq4HtTRGDTXoTPoGMIXBpIe4p1WBwFKCDmE=; b=y1fgTsI88SMLvJNWqQln49WkXTZRGTkVlxzQ3jICQjL/1ruaXGT9aGDu3zCpU1aZjx Y1Aafba0MsEl/mX7CqC59/ULyxFqNB00gu4/ufdEvRMYvGyuH2wITvrSEdwhE/99r5bu iZI9kYJkf8mg7FtNnkCzsCSSF2o3SKnZONPZg2Rbs4FxFw1GNLXF9BFOX9u06HsLzg+Q BrkLEeU06ab39pCgrp/8dieWSS9fC1ZBkDjP1XOT0Y/AhgBeJzr4SlHiaa+NzsBYY2lK ACtZD71cRcxQq/DCIDG7oj11+VMn1/sJ8VRZicos6MPkBsT3+kb5DB0LzopOj8e5tVCz MwBg== X-Gm-Message-State: AOAM531cQRpIpHc0ke6igoI9Vtlwn4+6So+s0DO8QXLHWvm7ILYD3ilg KgjcxjFM5minTkxX50Tcp4cuLP4bqQMlhMbBwDQQyxtbsxxaVA== X-Google-Smtp-Source: ABdhPJyou23AxKbMurRRWkN56d7ZfCB7SSCyJYHzKorNzZvcyYZP4I+zlTjrtZY3Mrv9z/ey5D6kJKavtu9kpR4tvqg= X-Received: by 2002:a67:f1d8:: with SMTP id v24mr1707584vsm.62.1640207948744; Wed, 22 Dec 2021 13:19:08 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: "Pedro Falcato" Date: Wed, 22 Dec 2021 21:18:56 +0000 Message-ID: Subject: Re: [edk2-devel] spurious CI failures To: edk2-devel-groups-io , "Kinney, Michael D" Cc: Ard Biesheuvel , Leif Lindholm , Sean Brogan , Bret Barkelew , "Kubacki, Michael" Content-Type: multipart/alternative; boundary="000000000000248b7305d3c2ac5b" --000000000000248b7305d3c2ac5b Content-Type: text/plain; charset="UTF-8" I do find it weird that Chocolatey is taking 45 minutes to install Qemu. Is this normal? I've never used Chocolatey but I've used plenty of package managers and none have ever taken this long to install something. Maybe it's Azure CI's problem? Anyway, is it not possible to cross-build qemu, as detailed in https://wiki.qemu.org/Hosts/W32#Cross_builds_2, in order to avoid any package manager issues? In the case that it's the package manager's problem. On Wed, Dec 22, 2021 at 8:27 PM Michael D Kinney wrote: > Hi Pedro, > > > > Thanks for the link to the log. I agree that log shows the choco install > is very slow and timeout out after 45 minutes. > > > > choco does support a flag to specify a larger timeout > (--execution-timeout). We can try increasing a bit higher as a temp > workaround. > > > > If choco is going to be this slow, we may have to use the caching > features of CI agents to cache these types of downloads > > so we only need to download when a version is updated. > > > > Mike > > > > *From:* devel@edk2.groups.io *On Behalf Of *Pedro > Falcato > *Sent:* Wednesday, December 22, 2021 11:22 AM > *To:* edk2-devel-groups-io ; Kinney, Michael D < > michael.d.kinney@intel.com> > *Cc:* Ard Biesheuvel ; Leif Lindholm ; > Sean Brogan ; Bret Barkelew < > Bret.Barkelew@microsoft.com>; Kubacki, Michael < > michael.kubacki@microsoft.com> > *Subject:* Re: [edk2-devel] spurious CI failures > > > > Hi Michael, > > > > I was curious when I read this email this morning and I found a log: > https://dev.azure.com/tianocore/edk2-ci/_build/results?buildId=36430&view=logs&j=417cab99-ad63-55d7-94dd-9898cfdbbe0e&t=5e8e03ff-365b-5151-1b77-4c25d18d4964 > > It looks like Chocolatey is taking way too long to download/install Qemu > (it's taking more than 2700 seconds). > > > > Best regards, > > Pedro > > > > On Wed, Dec 22, 2021 at 4:42 PM Michael D Kinney < > michael.d.kinney@intel.com> wrote: > > Hi Ard, > > Can you point me at some PRs that have this in their log? > > Thanks, > > Mike > > > -----Original Message----- > > From: Ard Biesheuvel > > Sent: Wednesday, December 22, 2021 1:43 AM > > To: edk2-devel-groups-io > > Cc: Leif Lindholm ; Kinney, Michael D < > michael.d.kinney@intel.com>; Sean Brogan ; > > Bret Barkelew ; Kubacki, Michael < > michael.kubacki@microsoft.com> > > Subject: spurious CI failures > > > > Hello all, > > > > In one out of ~5 attempts at pushing a PR to master, I get a failure > > at the following step > > > > "Install QEMU and Set QEMU on path" > > > > of the PlatformCI_OvmfPkg_Windows_VS2019_PR target. > > > > Is there any way we can remediate this? Or at least classify some > > failures as temporary, so it doesn't look like the failure has > > anything to do with the contents of the PR? > > > > Alternatively, a control for maintainers to override bogus CI results > > would help as well. > > > > Thanks, > > Ard. > > > > > > > > -- > > Pedro Falcato > > > > -- Pedro Falcato --000000000000248b7305d3c2ac5b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I do find it weird that Chocolatey is taking 45 minutes to= install Qemu. Is this normal? I've never used Chocolatey but I've = used plenty of package managers and none have ever taken this long to insta= ll something.

Maybe it's Azure CI's problem?

Anyway, is it not possible to cross-build qemu, as de= tailed in=C2=A0h= ttps://wiki.qemu.org/Hosts/W32#Cross_builds_2, in order to avoid any pa= ckage manager issues? In the case that it's the package manager's p= roblem.=C2=A0

On Wed, Dec 22, 2021 at 8:27 PM Michael D Kinney <michael.d.kinney@intel.com&g= t; wrote:

Hi Pedro,

=C2=A0

Thanks for the link to the log.=C2=A0 I agree that log shows the choco install is very slow and timeout out after 45 minutes= .

=C2=A0

choco does support a flag to specify a larger timeout (--execution-timeout).=C2=A0 We can try increasing a bit higher as a temp workaround.

=C2=A0

If choco is going to = be this slow, we may have to use the caching features of CI agents to cache= these types of downloads

so we only need to download when a version is = updated.

=C2=A0

Mike

=C2=A0

From: devel@edk2.groups.io <devel@edk2.groups.io= > On Behalf Of Pedro Falcato
Sent: Wednesday, December 22, 2021 11:22 AM
To: edk2-devel-groups-io <devel@edk2.groups.io>; Kinney, Michael D <michael.d.kinne= y@intel.com>
Cc: Ard Biesheuvel <ardb@kernel.org>; Leif Lindholm <leif@nuviainc.com>; Sean Brogan <<= a href=3D"mailto:sean.brogan@microsoft.com" target=3D"_blank">sean.brogan@m= icrosoft.com>; Bret Barkelew <Bret.Barkelew@microsoft.com>; Kubacki,= Michael <michael.kubacki@microsoft.com>
Subject: Re: [edk2-devel] spurious CI failures<= /p>

=C2=A0

Hi Michael,

=C2=A0

It looks like Chocolatey is taking way too long to d= ownload/install Qemu (it's taking more than 2700 seconds).

=C2=A0

Best regards,

Pedro

=C2=A0

On Wed, Dec 22, 2021 at 4:42 PM Michael D Kinney <= ;michael.d.= kinney@intel.com> wrote:

Hi Ard,

Can you point me at some PRs that have this in their log?

Thanks,

Mike

> -----Original Message-----
> From: Ard Biesheuvel <ardb@kernel.org>
> Sent: Wednesday, December 22, 2021 1:43 AM
> To: edk2-devel-groups-io <devel@edk2.groups.io>
> Cc: Leif Lindholm <leif@nuviainc.com>; Kinney, Michael D <michael.d.kinney@intel.com= >; Sean Brogan <sean.brogan@microsoft.com>;
> Bret Barkelew <Bret.Barkelew@microsoft.com>; Kubacki, Michael <michael.kuba= cki@microsoft.com>
> Subject: spurious CI failures
>
> Hello all,
>
> In one out of ~5 attempts at pushing a PR to master, I get a failure > at the following step
>
> "Install QEMU and Set QEMU on path"
>
> of the PlatformCI_OvmfPkg_Windows_VS2019_PR target.
>
> Is there any way we can remediate this? Or at least classify some
> failures as temporary, so it doesn't look like the failure has
> anything to do with the contents of the PR?
>
> Alternatively, a control for maintainers to override bogus CI results<= br> > would help as well.
>
> Thanks,
> Ard.





=C2=A0

--

Pedro Falcato

=20



--
Pedro Falcato
--000000000000248b7305d3c2ac5b--