From: "Rebecca Cran" <rebecca@bsdio.com>
To: devel@edk2.groups.io, ardb@kernel.org, "Wu, Hao A" <hao.a.wu@intel.com>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
Michael Kubacki <mikuback@linux.microsoft.com>,
Sean Brogan <sean.brogan@microsoft.com>
Subject: Re: [edk2-devel] failed pr
Date: Wed, 7 Jun 2023 09:39:03 -0600 [thread overview]
Message-ID: <04fbd5e9-0c0a-4432-015f-3fde86253161@bsdio.com> (raw)
In-Reply-To: <CAMj1kXGt36xWv-dxibTXL9fXgOR6j2de2SwOQSjccp=W02Rk9g@mail.gmail.com>
I've pushed it.
--
Rebecca Cran
On 6/7/23 09:09, Ard Biesheuvel wrote:
> I found the button too, and it works as expected.
>
> While the ongoing CI issues are investigated, could someone please
> push the button on this one? Thanks.
>
> https://github.com/tianocore/edk2/pull/4529
>
>
>
> On Wed, 7 Jun 2023 at 05:16, Wu, Hao A <hao.a.wu@intel.com> wrote:
>> Thanks. Below approach works for me:
>>
>>> From Conversation tab, scroll down to the "Some checks were not
>>> successful"
>>> area and scroll down to a check that failed. The select "Details".
>>> that will take you to the specific area of the Checks tab that contains
>>> a failure and the drop down for "Re-run failed checks" is available.
>> Best Regards,
>> Hao Wu
>>
>>> -----Original Message-----
>>> From: Kinney, Michael D <michael.d.kinney@intel.com>
>>> Sent: Wednesday, June 7, 2023 11:08 AM
>>> To: Wu, Hao A <hao.a.wu@intel.com>; devel@edk2.groups.io; Ard
>>> Biesheuvel <ardb@kernel.org>
>>> Cc: Michael Kubacki <mikuback@linux.microsoft.com>; Sean Brogan
>>> <sean.brogan@microsoft.com>; Kinney, Michael D
>>> <michael.d.kinney@intel.com>
>>> Subject: RE: [edk2-devel] failed pr
>>>
>>> There seems to be multiple views in the checks tab.
>>>
>>> From Conversation tab, scroll down to the "Some checks were not
>>> successful"
>>> area and scroll down to a check that failed. The select "Details".
>>> that will take you to the specific area of the Checks tab that contains
>>> a failure and the drop down for "Re-run failed checks" is available.
>>>
>>> Since we 4 groups of check jobs, you have to be in the right scope.
>>>
>>> From the checks tab, you can also select "Azure Pipelines" and scroll
>>> down to a failed check. Click on it, and "Re-run failed jobs" will be
>>> available. Most of the failures are in Azure Pipelines.
>>>
>>> Mike
>>>
>>>> -----Original Message-----
>>>> From: Wu, Hao A <hao.a.wu@intel.com>
>>>> Sent: Tuesday, June 6, 2023 7:02 PM
>>>> To: devel@edk2.groups.io; Kinney, Michael D
>>> <michael.d.kinney@intel.com>;
>>>> Ard Biesheuvel <ardb@kernel.org>
>>>> Cc: Michael Kubacki <mikuback@linux.microsoft.com>; Sean Brogan
>>>> <sean.brogan@microsoft.com>
>>>> Subject: RE: [edk2-devel] failed pr
>>>>
>>>> Hello Mike,
>>>>
>>>> I do not see the "re-run failed jobs" under "Checks" tab for cancelled CI
>>>> tests:
>>>> https://github.com/tianocore/edk2/pull/4478
>>>> (Only "Re-run all checks" is found)
>>>>
>>>> What should be done to handle such case?
>>>>
>>>> Best Regards,
>>>> Hao Wu
>>>>
>>>>> -----Original Message-----
>>>>> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of
>>> Michael
>>>>> D Kinney
>>>>> Sent: Wednesday, June 7, 2023 3:55 AM
>>>>> To: Ard Biesheuvel <ardb@kernel.org>; devel@edk2.groups.io
>>>>> Cc: Michael Kubacki <mikuback@linux.microsoft.com>; Sean Brogan
>>>>> <sean.brogan@microsoft.com>; Kinney, Michael D
>>>>> <michael.d.kinney@intel.com>
>>>>> Subject: Re: [edk2-devel] failed pr
>>>>>
>>>>> All EDK II Maintainers should now have permissions to "re-run failed
>>>> jobs".
>>>>> If you see a PR with failed jobs that are not related to the code change,
>>>> then
>>>>> try rerunning the specific failed job or select "re-run failed jobs"
>>>>> from the drop down in top right of "Checks" tab.
>>>>>
>>>>> Please let me know if you do not see this as an option.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Mike
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Kinney, Michael D <michael.d.kinney@intel.com>
>>>>>> Sent: Friday, June 2, 2023 5:07 PM
>>>>>> To: Ard Biesheuvel <ardb@kernel.org>; devel@edk2.groups.io
>>>>>> Cc: Michael Kubacki <mikuback@linux.microsoft.com>; Sean Brogan
>>>>>> <sean.brogan@microsoft.com>; Kinney, Michael D
>>>>>> <michael.d.kinney@intel.com>
>>>>>> Subject: RE: [edk2-devel] failed pr
>>>>>>
>>>>>> Merged
>>>>>>
>>>>>> Mike
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Ard Biesheuvel <ardb@kernel.org>
>>>>>>> Sent: Friday, June 2, 2023 4:39 PM
>>>>>>> To: devel@edk2.groups.io; Kinney, Michael D
>>>>>>> <michael.d.kinney@intel.com>
>>>>>>> Cc: Michael Kubacki <mikuback@linux.microsoft.com>; Sean Brogan
>>>>>>> <sean.brogan@microsoft.com>
>>>>>>> Subject: Re: [edk2-devel] failed pr
>>>>>>>
>>>>>>> Another one
>>>>>>>
>>>>>>> https://github.com/tianocore/edk2/pull/4473
>>>>>>>
>>>>>>> On Sat, 3 Jun 2023 at 00:32, Ard Biesheuvel <ardb@kernel.org> wrote:
>>>>>>>> Thanks!
>>>>>>>>
>>>>>>>> On Fri, 2 Jun 2023 at 18:38, Michael D Kinney
>>>>>>>> <michael.d.kinney@intel.com> wrote:
>>>>>>>>> Done.
>>>>>>>>>
>>>>>>>>> Mike
>>>>>>>>>
>>>>>>>>>> -----Original Message-----
>>>>>>>>>> From: Kinney, Michael D <michael.d.kinney@intel.com>
>>>>>>>>>> Sent: Friday, June 2, 2023 9:37 AM
>>>>>>>>>> To: devel@edk2.groups.io; ardb@kernel.org; Michael Kubacki
>>>>>>>>>> <mikuback@linux.microsoft.com>; Sean Brogan
>>>>>>> <sean.brogan@microsoft.com>
>>>>>>>>>> Cc: Kinney, Michael D <michael.d.kinney@intel.com>
>>>>>>>>>> Subject: RE: [edk2-devel] failed pr
>>>>>>>>>>
>>>>>>>>>> I am working on it.
>>>>>>>>>>
>>>>>>>>>> Mike
>>>>>>>>>>
>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>> From: devel@edk2.groups.io <devel@edk2.groups.io> On
>>> Behalf
>>>>>>>>>>> Of
>>>>>> Ard
>>>>>>>>>>> Biesheuvel
>>>>>>>>>>> Sent: Friday, June 2, 2023 9:19 AM
>>>>>>>>>>> To: Kinney, Michael D <michael.d.kinney@intel.com>; Michael
>>>>>> Kubacki
>>>>>>>>>>> <mikuback@linux.microsoft.com>; Sean Brogan
>>>>>>> <sean.brogan@microsoft.com>;
>>>>>>>>>>> edk2-devel-groups-io <devel@edk2.groups.io>
>>>>>>>>>>> Subject: [edk2-devel] failed pr
>>>>>>>>>>>
>>>>>>>>>>> Could someone push the merge button on this pr please?
>>>>>>>>>>>
>>>>>>>>>>> https://github.com/tianocore/edk2/pull/4470
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>
>>>>>
>
>
>
>
next prev parent reply other threads:[~2023-06-07 15:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2023-06-07 17:00 ` Ard Biesheuvel
2023-06-07 17:02 ` Rebecca Cran
2023-06-07 17:03 ` Ard Biesheuvel
-- strict thread matches above, loose matches on Subject: below --
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
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
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=04fbd5e9-0c0a-4432-015f-3fde86253161@bsdio.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