From: "Sean" <spbrogan@outlook.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"ardb@kernel.org" <ardb@kernel.org>,
Rebecca Cran <rebecca@bsdio.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
Michael Kinney <michael.d.kinney@intel.com>,
Michael Kubacki <michael.kubacki@microsoft.com>,
"Liming Gao (Byosoft address)" <gaoliming@byosoft.com.cn>
Subject: Re: [edk2-devel] failed Pr
Date: Mon, 29 May 2023 15:12:07 +0000 [thread overview]
Message-ID: <BY3PR19MB490077B028D09FB28B45832EC84A9@BY3PR19MB4900.namprd19.prod.outlook.com> (raw)
In-Reply-To: <CAMj1kXEhMjPCmD9QiP_nKK4NGQJnExmA1nY0ykpUBNz_j8A6gQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1524 bytes --]
It has been rerun.
________________________________
From: devel@edk2.groups.io <devel@edk2.groups.io> on behalf of Ard Biesheuvel <ardb@kernel.org>
Sent: Monday, May 29, 2023 7:44:37 AM
To: Rebecca Cran <rebecca@bsdio.com>
Cc: devel@edk2.groups.io <devel@edk2.groups.io>; Michael Kinney <michael.d.kinney@intel.com>; Michael Kubacki <michael.kubacki@microsoft.com>; Liming Gao (Byosoft address) <gaoliming@byosoft.com.cn>
Subject: Re: [edk2-devel] failed Pr
On Mon, 29 May 2023 at 16:37, Rebecca Cran <rebecca@bsdio.com> wrote:
>
> It looks like the agent or machine running the CI task crashed.
>
> "##[error]We stopped hearing from agent Azure Pipelines 18. Verify the
> agent machine is running and has a healthy network connection. Anything
> that terminates an agent process, starves it for CPU, or blocks its
> network access can cause this error. For more information, see:
> https://go.microsoft.com/fwlink/?linkid=846610"
>
Hmm, it would be nice if this thing could distinguish between 'error
in your code' and 'internal error' where the latter does not mark your
PR as being rejected.
>
>
>
>
> The only way I've found to make CI run again is to do something to cause
> the commit hash to change, for example by making a change to ReadMe.rst
> then reverting it.
>
Mike Kinney mentioned last time that there is a button I could push. Mike?
I am reluctant to make unnecessary changes to the state of the branch
just to trick the CI into having another go at it.
[-- Attachment #2: Type: text/html, Size: 2455 bytes --]
next prev parent reply other threads:[~2023-05-29 15:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 12:48 failed Pr Ard Biesheuvel
2023-05-29 12:55 ` [edk2-devel] " Attar, AbdulLateef (Abdul Lateef)
2023-05-29 14:37 ` Rebecca Cran
2023-05-29 14:44 ` Ard Biesheuvel
2023-05-29 15:12 ` Sean [this message]
2023-05-29 15:13 ` Michael D Kinney
2023-05-29 15:37 ` Sean
2023-05-29 15:43 ` Rebecca Cran
2023-05-29 16:44 ` Michael D Kinney
2023-05-30 14:36 ` Ard Biesheuvel
2023-05-30 15:34 ` Michael D Kinney
2023-05-30 15:45 ` Ard Biesheuvel
2023-05-30 17:26 ` Michael D Kinney
-- strict thread matches above, loose matches on Subject: below --
2023-06-02 16:19 failed pr Ard Biesheuvel
2023-06-02 16:36 ` [edk2-devel] " Michael D Kinney
2023-06-02 16:38 ` Michael D Kinney
2023-06-02 22:32 ` Ard Biesheuvel
2023-06-02 23:38 ` Ard Biesheuvel
2023-06-03 0:07 ` Michael D Kinney
2023-06-06 19:55 ` Michael D Kinney
2023-06-06 21:37 ` Ard Biesheuvel
2023-06-07 2:02 ` Wu, Hao A
2023-06-07 3:07 ` Michael D Kinney
2023-06-07 3:15 ` Wu, Hao A
2023-06-07 15:09 ` Ard Biesheuvel
2023-06-07 15:39 ` Rebecca Cran
2023-06-07 17:00 ` Ard Biesheuvel
2023-06-07 17:02 ` Rebecca Cran
2023-06-07 17:03 ` Ard Biesheuvel
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=BY3PR19MB490077B028D09FB28B45832EC84A9@BY3PR19MB4900.namprd19.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