public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ardb@kernel.org>
To: Michael Kubacki <Michael.Kubacki@microsoft.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	 "mikuback@linux.microsoft.com" <mikuback@linux.microsoft.com>,
	Sunil V L <sunilvl@ventanamicro.com>,
	 Sean Brogan <sean.brogan@microsoft.com>,
	 "Kinney, Michael D" <michael.d.kinney@intel.com>,
	 "Liming Gao (Byosoft address)" <gaoliming@byosoft.com.cn>,
	Leif Lindholm <quic_llindhol@quicinc.com>,
	 Abner Chang <abner.chang@amd.com>,
	Daniel Schaefer <git@danielschaefer.me>
Subject: Re: [edk2-devel] [PATCH] EmbeddedPkg/PrePiLib: Drop unused PCD PcdPrePiCpuIoSize
Date: Mon, 6 Feb 2023 23:41:46 +0100	[thread overview]
Message-ID: <CAMj1kXHpeC1EWObWdtFkp5P1zq-ehtwe3M_E-+NTTFSDBCjRNg@mail.gmail.com> (raw)
In-Reply-To: <LV2PR21MB3351599CF30FDDDE8C4E13CBF4DA9@LV2PR21MB3351.namprd21.prod.outlook.com>

On Mon, 6 Feb 2023 at 23:40, Michael Kubacki
<Michael.Kubacki@microsoft.com> wrote:
>
> While CI involves several services, in the future you can check the following dashboard for any known widespread Pipeline service issues:
> https://status.dev.azure.com/
>
> In my experience though, issues (which are relatively rare) are usually in some other component executed after the agent is acquired which I suspect was the case here.
>

Thanks,

> -----Original Message-----
> From: Ard Biesheuvel <ardb@kernel.org>
> Sent: Monday, February 6, 2023 5:04 PM
> To: devel@edk2.groups.io; mikuback@linux.microsoft.com
> Cc: Sunil V L <sunilvl@ventanamicro.com>; Sean Brogan <sean.brogan@microsoft.com>; Kinney, Michael D <michael.d.kinney@intel.com>; Liming Gao (Byosoft address) <gaoliming@byosoft.com.cn>; Michael Kubacki <Michael.Kubacki@microsoft.com>; Leif Lindholm <quic_llindhol@quicinc.com>; Abner Chang <abner.chang@amd.com>; Daniel Schaefer <git@danielschaefer.me>
> Subject: [EXTERNAL] Re: [edk2-devel] [PATCH] EmbeddedPkg/PrePiLib: Drop unused PCD PcdPrePiCpuIoSize
>
> On Sat, 4 Feb 2023 at 02:26, Michael Kubacki <mikuback@linux.microsoft.com> wrote:
> >
> > Hi Ard,
> >
> > I'm not an admin on the tianocore Azure DevOps organization so I
> > cannot view or do much more than you can.
> >
> > It appears to me to be a transient issue during provisioning on the
> > particular agent. Normally, I'd use a "rerun failed jobs" button to
> > see if it continues to repro as a next step.
> >
> > A push to the PR branch will do the same thing. If you haven't
> > already, can you try doing another push to kick off the builds again
> > and see if it reoccurs?
> >
>
> Guess this was just a glitch - I tried again the next day and it went through with no issues.
>
> Thanks,

  reply	other threads:[~2023-02-06 22:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03 11:08 [PATCH] EmbeddedPkg/PrePiLib: Drop unused PCD PcdPrePiCpuIoSize Ard Biesheuvel
2023-02-03 11:16 ` Sunil V L
2023-02-03 11:48   ` Ard Biesheuvel
2023-02-04  1:26     ` [edk2-devel] " Michael Kubacki
2023-02-06 22:04       ` Ard Biesheuvel
2023-02-06 22:40         ` Michael Kubacki
2023-02-06 22:41           ` Ard Biesheuvel [this message]
2023-02-04  1:27     ` EDKII -CI weird issue Yao, Jiewen
2023-02-04  1:39       ` Michael D Kinney
2023-02-04 11:32         ` Yao, Jiewen

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=CAMj1kXHpeC1EWObWdtFkp5P1zq-ehtwe3M_E-+NTTFSDBCjRNg@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