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.52483.1685374991738125526 for ; Mon, 29 May 2023 08:43:12 -0700 Authentication-Results: mx.groups.io; dkim=fail reason="signature has expired" header.i=@bsdio.com header.s=fm2 header.b=K35MT6/z; spf=pass (domain: bsdio.com, ip: 66.111.4.29, mailfrom: rebecca@bsdio.com) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id EA8A75C0139; Mon, 29 May 2023 11:43:10 -0400 (EDT) Received: from imap43 ([10.202.2.93]) by compute5.internal (MEProxy); Mon, 29 May 2023 11:43:10 -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= 1685374990; x=1685461390; bh=NVbJ73zrH3/NPf8o2kOEley3XTdnhbTzN0v JjaA1rcI=; b=K35MT6/zY/x11CqqJsCcvvp3YygXjVbpeI45+cW33mxWlCjCOPq dTde7VLp9V4h9bWzV1APw3naBDd0R3eGvhJGT5fEbmJ4oGNE2nJ1yDJ+JLCns2FK s/pVh5cw85bN5cHBIbxWU6ZfBwaMbqGdL8i0K4UDkfwFkptk/BRbJrDvU8O2uyae ANX44mmUTHCPsWSpAdv4Gfuk4oJJQeR3046LY0ukfYrSW+KxeB2V1z2+NkVxunZT xz7OH0nPYcFcLK+qYYSUohRe3fTfU/T3JKEWYfzkcmoha7OxlYtQcxcXwg7PMgLQ h/ZkxSdAar/86OhscPD9SSdey5HZm8Jw7uQ== 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= 1685374990; x=1685461390; bh=NVbJ73zrH3/NPf8o2kOEley3XTdnhbTzN0v JjaA1rcI=; b=qtJfwJijDGQerrceiQFYaEgXa3XLthPHEdKqm266Zm3dUmphIuQ YlClxCrsw2v+Vq85MpUUDuh/nuNDfPBOSdJcKx7+f72uMkfN0ZjM/MFJS/95EK1e jOzZJ6r6PmzNuE2C+H/4W5i8AVUplQMU4AWTygnGqXxreJV1aWZHUBK1E1bY57aP vbR6zTrv/SvL1uBtb9+nVJXfIYd+YuZf+IUVZlDwxKkYu9lM1Ts+ipc8ovnxF8qc Vz6dQVGgz303Nq+9JWEZ4AnyZKOPO25WRUiFVWVSXDk3Ek9Rpvd4u7boFmybeM3T g62gYYv5RdGr9PEorye6Gbu9nP2+mn/XnZg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeekhedgleduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvfevufgtgfesthhqredtreerjeenucfhrhhomhepfdft vggsvggttggrucevrhgrnhdfuceorhgvsggvtggtrgessghsughiohdrtghomheqnecugg ftrfgrthhtvghrnhepvdeugfekveegffegheevgeekgeejgeekhedvhfdvfffhjeejfeeu gfefieeuledvnecuffhomhgrihhnpehmihgtrhhoshhofhhtrdgtohhmpdhgrhhouhhpsh drihhonecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhep rhgvsggvtggtrgessghsughiohdrtghomh X-ME-Proxy: Feedback-ID: i5b994698:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 270B22D40090; Mon, 29 May 2023 11:43:10 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.9.0-alpha0-441-ga3ab13cd6d-fm-20230517.001-ga3ab13cd Mime-Version: 1.0 Message-Id: <64a286dd-5145-4dab-aed5-f4dbd3f96c9d@app.fastmail.com> In-Reply-To: References: <4bcb9012-7e12-9df0-59a4-aff46b911c8f@bsdio.com> Date: Mon, 29 May 2023 09:43:09 -0600 From: "Rebecca Cran" To: devel@edk2.groups.io, spbrogan@outlook.com, "Kinney, Michael D" , "Ard Biesheuvel" Cc: "Kubacki, Michael" , gaoliming Subject: Re: [edk2-devel] failed Pr Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable I pay for a Visual Studio subscription, so I shouldn=E2=80=99t count toward= s the limit then. My GitHub email address is the same as I use here. =E2=80=94=20 Rebecca On Mon, May 29, 2023, at 9:37 AM, Sean wrote: > It has changed over time and I no longer see a button on the "checks"=20 > page of GitHub. I only see the button in the azure pipeline which=20 > would mean maintainers would need to be "contributors" in the azure=20 > DevOps organization/project. I have no problem with that and it looks=20 > like you can sign in with a GitHub account so it should just be a=20 > matter of collecting the email address associated with their GitHub and= =20 > inviting them to join. We only get 5 free basic users but we get=20 > unlimited free "stakeholder" accounts. I assume we might need basic=20 > accounts to interact with the pipeline stuff but I don't know for sure.= =20 > Anyone who has paid Microsoft visual studio subscriptions (like from=20 > an employer) usually doesn't count towards the 5. =20 > > Regardless for those actively contributing and interested we should add= =20 > them up to the limit. This was one of the reasons we had desired long=20 > term to align on GitHub build services instead. > > Other thoughts? > > Thanks > Sean=20 > *From:* Kinney, Michael D > *Sent:* Monday, May 29, 2023 8:13:32 AM > *To:* devel@edk2.groups.io ; spbrogan@outlook.com= =20 > ; ardb@kernel.org ; Rebecca Cran= =20 > > *Cc:* Kubacki, Michael ; Gao, Liming=20 > ; Kinney, Michael D=20 > > *Subject:* RE: [edk2-devel] failed Pr=20 >=20 > Hi Sean, > >=20 > > Do you know what GitHub permissions are required to see the re-run button= ? > >=20 > > I think it is reasonable for all Maintainers to have that available. > >=20 > > Mike > >=20 > > *From:* devel@edk2.groups.io * On Behalf Of *Sean > *Sent:* Monday, May 29, 2023 8:12 AM > *To:* devel@edk2.groups.io; ardb@kernel.org; Rebecca Cran=20 > > *Cc:* devel@edk2.groups.io; Kinney, Michael D=20 > ; Kubacki, Michael=20 > ; Gao, Liming > *Subject:* Re: [edk2-devel] failed Pr > >=20 > > It has been rerun.=20 > >=20 > > *From:* devel@edk2.groups.io on behalf of Ard=20 > Biesheuvel > *Sent:* Monday, May 29, 2023 7:44:37 AM > *To:* Rebecca Cran > *Cc:* devel@edk2.groups.io ; Michael Kinney=20 > ; Michael Kubacki=20 > ; Liming Gao (Byosoft address)=20 > > *Subject:* Re: [edk2-devel] failed Pr=20 > >=20 > > On Mon, 29 May 2023 at 16:37, Rebecca Cran 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=3D846610" >> > > 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. > > > > > > >=20