From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by mx.groups.io with SMTP id smtpd.web11.1480.1686152346784827404 for ; Wed, 07 Jun 2023 08:39:07 -0700 Authentication-Results: mx.groups.io; dkim=fail reason="signature has expired" header.i=@bsdio.com header.s=fm2 header.b=vtVeYJeZ; spf=pass (domain: bsdio.com, ip: 66.111.4.29, mailfrom: rebecca@bsdio.com) Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 261965C0082; Wed, 7 Jun 2023 11:39:06 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Wed, 07 Jun 2023 11:39:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdio.com; h=cc :cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm2; t= 1686152346; x=1686238746; bh=XiinaVPVLxmwsL9zNyP5dDPaqQI8hvCPCLI A7OY50tY=; b=vtVeYJeZ3mKiUqGQ/NcVWKPCGdWI+9P4oiD2ZSp7Axp0z1vXNHL smYZXbrLRd+aorjyKfgqw1Y6IcMEiqZoNCIxO5J65DdBuUSh1BBmGmk9mQ8n5ktX o7JspOzVMNliEdWfWX9JwnOJzRue0Uxk261be1C3VQNgclFgehSqm8MFwPK2QNfM IiYgDovyIjPDA3H1Ylxc6o9VfK+uAPqwNhae0XgwQvE9xzEY+8PNhJ8rtIgMOytw wvb3et+zxF4UOBJZbszPuO8wpq+z4N0NMQqvuodOqFkx2Ons0bD740+8VlFaLfOh /hhrkjRHAKhgWYQl/AgofAkCMfLxWMFabFw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1686152346; x=1686238746; bh=XiinaVPVLxmwsL9zNyP5dDPaqQI8hvCPCLI A7OY50tY=; b=RvXX4YKenjMYJknLaH8exv++1DPutvpp3BtiQ9w8cWRB0FzkXTh Hvf4l4TWSE/UmuI9Jy63DlP1SJftvHweDP2lgr4F5bG/5gV5qP1DiEP3UgKAMf5X Wv/6Kh/LY4tQeGrQuIEIRlE6f/5YKmQxVl24GQk94SouRk9NC9GsFV77hFN2Jm+I bILz8cgjr3jgAlRA++hU8VZ1BoStu6wA1WfYUkwoiS9XhNWKvEe0Tf0xXiW2SQwZ QZZ1Y/577hun1uw36PLpXXlsZgqJEWkrinAT8dwOJ6gkh1gvT40GLr2nQjP6JasM 5M68FT+6qAMvmCeG0m4ByKssYYI86UDTvEg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrgedtgedgleduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpeftvggs vggttggrucevrhgrnhcuoehrvggsvggttggrsegsshguihhordgtohhmqeenucggtffrrg htthgvrhhnpeeugeffudehtdffieelgeelvdehudehgfekueevvdeuudelffdtheehieeg jeeileenucffohhmrghinhepghhithhhuhgsrdgtohhmnecuvehluhhsthgvrhfuihiivg eptdenucfrrghrrghmpehmrghilhhfrhhomheprhgvsggvtggtrgessghsughiohdrtgho mh X-ME-Proxy: Feedback-ID: i5b994698:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 7 Jun 2023 11:39:04 -0400 (EDT) Message-ID: <04fbd5e9-0c0a-4432-015f-3fde86253161@bsdio.com> Date: Wed, 7 Jun 2023 09:39:03 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: [edk2-devel] failed pr To: devel@edk2.groups.io, ardb@kernel.org, "Wu, Hao A" Cc: "Kinney, Michael D" , Michael Kubacki , Sean Brogan References: From: "Rebecca Cran" In-Reply-To: Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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 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 >>> Sent: Wednesday, June 7, 2023 11:08 AM >>> To: Wu, Hao A ; devel@edk2.groups.io; Ard >>> Biesheuvel >>> Cc: Michael Kubacki ; Sean Brogan >>> ; Kinney, Michael D >>> >>> 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 >>>> Sent: Tuesday, June 6, 2023 7:02 PM >>>> To: devel@edk2.groups.io; Kinney, Michael D >>> ; >>>> Ard Biesheuvel >>>> Cc: Michael Kubacki ; Sean Brogan >>>> >>>> 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 On Behalf Of >>> Michael >>>>> D Kinney >>>>> Sent: Wednesday, June 7, 2023 3:55 AM >>>>> To: Ard Biesheuvel ; devel@edk2.groups.io >>>>> Cc: Michael Kubacki ; Sean Brogan >>>>> ; Kinney, Michael D >>>>> >>>>> 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 >>>>>> Sent: Friday, June 2, 2023 5:07 PM >>>>>> To: Ard Biesheuvel ; devel@edk2.groups.io >>>>>> Cc: Michael Kubacki ; Sean Brogan >>>>>> ; Kinney, Michael D >>>>>> >>>>>> Subject: RE: [edk2-devel] failed pr >>>>>> >>>>>> Merged >>>>>> >>>>>> Mike >>>>>> >>>>>>> -----Original Message----- >>>>>>> From: Ard Biesheuvel >>>>>>> Sent: Friday, June 2, 2023 4:39 PM >>>>>>> To: devel@edk2.groups.io; Kinney, Michael D >>>>>>> >>>>>>> Cc: Michael Kubacki ; Sean Brogan >>>>>>> >>>>>>> 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 wrote: >>>>>>>> Thanks! >>>>>>>> >>>>>>>> On Fri, 2 Jun 2023 at 18:38, Michael D Kinney >>>>>>>> wrote: >>>>>>>>> Done. >>>>>>>>> >>>>>>>>> Mike >>>>>>>>> >>>>>>>>>> -----Original Message----- >>>>>>>>>> From: Kinney, Michael D >>>>>>>>>> Sent: Friday, June 2, 2023 9:37 AM >>>>>>>>>> To: devel@edk2.groups.io; ardb@kernel.org; Michael Kubacki >>>>>>>>>> ; Sean Brogan >>>>>>> >>>>>>>>>> Cc: Kinney, Michael D >>>>>>>>>> Subject: RE: [edk2-devel] failed pr >>>>>>>>>> >>>>>>>>>> I am working on it. >>>>>>>>>> >>>>>>>>>> Mike >>>>>>>>>> >>>>>>>>>>> -----Original Message----- >>>>>>>>>>> From: devel@edk2.groups.io On >>> Behalf >>>>>>>>>>> Of >>>>>> Ard >>>>>>>>>>> Biesheuvel >>>>>>>>>>> Sent: Friday, June 2, 2023 9:19 AM >>>>>>>>>>> To: Kinney, Michael D ; Michael >>>>>> Kubacki >>>>>>>>>>> ; Sean Brogan >>>>>>> ; >>>>>>>>>>> edk2-devel-groups-io >>>>>>>>>>> Subject: [edk2-devel] failed pr >>>>>>>>>>> >>>>>>>>>>> Could someone push the merge button on this pr please? >>>>>>>>>>> >>>>>>>>>>> https://github.com/tianocore/edk2/pull/4470 >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>> >>>>> >>>>> > > > >