public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: Ard Biesheuvel <ardb@kernel.org>,
	edk2-devel-groups-io <devel@edk2.groups.io>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: 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: spurious CI failures
Date: Wed, 22 Dec 2021 16:41:14 +0000	[thread overview]
Message-ID: <CO1PR11MB4929F29007D333E583001ABAD27D9@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAMj1kXGAs0GPXV9ZJjnNP7u8QEN6fytMtSvS9Y9CNACm-he0Jg@mail.gmail.com>

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.

  reply	other threads:[~2021-12-22 16:42 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 [this message]
2021-12-22 19:22   ` [edk2-devel] " Pedro Falcato
2021-12-22 20:27     ` 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=CO1PR11MB4929F29007D333E583001ABAD27D9@CO1PR11MB4929.namprd11.prod.outlook.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