public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Pedro Falcato" <pedro.falcato@gmail.com>
To: edk2-devel-groups-io <devel@edk2.groups.io>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: Ard Biesheuvel <ardb@kernel.org>,
	Leif Lindholm <leif@nuviainc.com>,
	 Sean Brogan <sean.brogan@microsoft.com>,
	Bret Barkelew <Bret.Barkelew@microsoft.com>,
	 "Kubacki, Michael" <michael.kubacki@microsoft.com>
Subject: Re: [edk2-devel] spurious CI failures
Date: Wed, 22 Dec 2021 19:22:06 +0000	[thread overview]
Message-ID: <CAKbZUD1-Upwt69bmWxCnQb1HOaMRqGD1Z+7bCBpPyJzScp-OXA@mail.gmail.com> (raw)
In-Reply-To: <CO1PR11MB4929F29007D333E583001ABAD27D9@CO1PR11MB4929.namprd11.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1570 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 2905 bytes --]

  reply	other threads:[~2021-12-22 19:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-22  9:43 spurious CI failures Ard Biesheuvel
2021-12-22 16:41 ` Michael D Kinney
2021-12-22 19:22   ` Pedro Falcato [this message]
2021-12-22 20:27     ` [edk2-devel] " Michael D Kinney
2021-12-22 21:18       ` Pedro Falcato
2021-12-22 22:45         ` Michael D Kinney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKbZUD1-Upwt69bmWxCnQb1HOaMRqGD1Z+7bCBpPyJzScp-OXA@mail.gmail.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox