From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by mx.groups.io with SMTP id smtpd.web10.53879.1685378698202891000 for ; Mon, 29 May 2023 09:44:58 -0700 Authentication-Results: mx.groups.io; dkim=fail reason="unable to parse pub key" header.i=@intel.com header.s=intel header.b=inRlH3OI; spf=pass (domain: intel.com, ip: 192.55.52.136, mailfrom: michael.d.kinney@intel.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1685378698; x=1716914698; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=HKdv4wpE8ALeJSdqYhiYdWSDaGMkVwI5axJJEeJidhs=; b=inRlH3OIZdqhIRce1ilgYXwMmRzDSIezbjXZGWLWueIbHfKFO/OBINFZ vuDFB2AnxFoeNaPX2tMq4Tlx/o1l7BxLZy+h1LUS7roPnwZuGu5wJdViK v51B2M8QPcKqDm53F19BOy4+og2E5H/c8774NJAeAOsjhAGB1g+zo1vaG v3Ji6hm2SjjbG/eKb2EggkllmGlyrtdLxJZ3tuseuZxxw9DthZcVDLHE0 W97jX3UcbQ1iAg8HQfbhIBz6m4VdLg4YNVVY5pcp2fcZzFhYjaBLpW3q5 lX9ARjOJ4QDFC+rJ5tirtl9lUMr0rvhPWuNW4v3PKfRbBQRgo2tKOc8I2 g==; X-IronPort-AV: E=McAfee;i="6600,9927,10725"; a="334364337" X-IronPort-AV: E=Sophos;i="6.00,201,1681196400"; d="scan'208,217";a="334364337" Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 May 2023 09:44:57 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10725"; a="952816365" X-IronPort-AV: E=Sophos;i="6.00,201,1681196400"; d="scan'208,217";a="952816365" Received: from orsmsx602.amr.corp.intel.com ([10.22.229.15]) by fmsmga006.fm.intel.com with ESMTP; 29 May 2023 09:44:57 -0700 Received: from orsmsx611.amr.corp.intel.com (10.22.229.24) by ORSMSX602.amr.corp.intel.com (10.22.229.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.23; Mon, 29 May 2023 09:44:56 -0700 Received: from orsmsx610.amr.corp.intel.com (10.22.229.23) by ORSMSX611.amr.corp.intel.com (10.22.229.24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.23; Mon, 29 May 2023 09:44:56 -0700 Received: from ORSEDG602.ED.cps.intel.com (10.7.248.7) by orsmsx610.amr.corp.intel.com (10.22.229.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.23 via Frontend Transport; Mon, 29 May 2023 09:44:56 -0700 Received: from NAM11-CO1-obe.outbound.protection.outlook.com (104.47.56.171) by edgegateway.intel.com (134.134.137.103) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.23; Mon, 29 May 2023 09:44:55 -0700 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=flaB8GSC/9Hc35xSgT7QunF/7+XFac2Ag6brFtJgomOSFQ6s6ax0NJa84rpVfx0kaz4wecFVesoiqhV0+Jy6i1x/PXggBQzfzn8peufCnljsejlxbGmdp3oFCQTwtciwEDBwxbsz010dXIj1EIZ5u3EauA+kso5ruJJ0vQ6cVIFOOxqPp0iQ9JqHQzie/dOMOxD6nzsKA6iEBL3m3d7aeYF8D0YEzNwuDyeEMrXNxaAJbn8zcN9pQY8QaKCY4CbY/yZPZiPZWbx6pGS7f8NfBg2L3T6cBvShQKp4ztV/HYEHo/OvL2FcelPRdusDNRCvQhekv5a41qLwo/Va6gsUgw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=wRCQW1JhLVqg+O6YTlVXiCZWn6SeV6P2yntKMEFgF5w=; b=E2uIkrDtSRQCgDyf5OjJWth/dosj9q3DnixhrofF+y65zYWH+JD+uxU50+oCEHdwN8keRB1VVuzMibZ7qpUx966IBLsu588f+9xdDCfiqwqpwC8MbhMbthRE1cvcsiZWHs4a53mZlc2+5NHwA2R8ESTMKqU3N9opzxYdQD20vQHjkqrzzhuMNjdPdXgEyxF7Tu+csveDeknMUXm5QceVMwrlNMXSubr/oSvP1HEc63FboSreTWDN/fia5FWOkFxQWUluQPXnEYYX16GqEiuODasoiGzcvQ4vmoTBzp/yAoURRQ0q623ktNJd/gHiCSyFY/ni98pGQE5HpICshimkrQ== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=intel.com; dmarc=pass action=none header.from=intel.com; dkim=pass header.d=intel.com; arc=none Received: from CO1PR11MB4929.namprd11.prod.outlook.com (2603:10b6:303:6d::19) by PH8PR11MB7144.namprd11.prod.outlook.com (2603:10b6:510:22c::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6433.22; Mon, 29 May 2023 16:44:53 +0000 Received: from CO1PR11MB4929.namprd11.prod.outlook.com ([fe80::4752:67f2:9956:b277]) by CO1PR11MB4929.namprd11.prod.outlook.com ([fe80::4752:67f2:9956:b277%4]) with mapi id 15.20.6433.018; Mon, 29 May 2023 16:44:53 +0000 From: "Michael D Kinney" To: Sean Brogan , "devel@edk2.groups.io" , "ardb@kernel.org" , Rebecca Cran CC: "Kubacki, Michael" , "Gao, Liming" , "Kinney, Michael D" Subject: Re: [edk2-devel] failed Pr Thread-Topic: [edk2-devel] failed Pr Thread-Index: AQHZkivxgn1yq7dppEyX0nCba8GaAa9xUfCAgAAB5oCAAAevgIAAADJQgAAG3ACAAA3MoA== Date: Mon, 29 May 2023 16:44:53 +0000 Message-ID: References: <4bcb9012-7e12-9df0-59a4-aff46b911c8f@bsdio.com> In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=intel.com; x-ms-publictraffictype: Email x-ms-traffictypediagnostic: CO1PR11MB4929:EE_|PH8PR11MB7144:EE_ x-ms-office365-filtering-correlation-id: 3064ddc5-0fc9-48f0-cb27-08db60640701 x-ld-processed: 46c98d88-e344-4ed4-8496-4ed7712e255d,ExtAddr x-ms-exchange-senderadcheck: 1 x-ms-exchange-antispam-relay: 0 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: OgR+OhhEGOyoRgGPK7ZDwuI80nLLTirSKpj75bhpTGh03+/MWLY7ornt+QSHHiODnWgJQFip8GQ6mR+cGMGeEhgD5TIak7+PVuh28VFDu1DN+JABNNAGWRWl12dl5t4sTJ4JKip3smKBBLe1PwWvLD3a07/ZOJYesVSiHXhrnfQ6eNIPyLjxr8kew9hKLF6GATH5o72a+mvq4ESu39qjGTp14+p1ajhtLybHeN/BCYMtA78uTkdl4C9p/XYAFADk3MoZtQEnE6psBVe1MMu6LvJnUiGJSDgHHRchO+Sytky8ctIS8vfv1FPDzPRCjiiBhuVMBiK8MZBdCVRhNXEU0iy3lWw6TD6GZLWVkKN5HOh91zcDEUYhzBMggXRylZKjc4owCfBE6kNxWzexWuDJWlGbU1WgmPOjR7BFyRsEA5Dcdx2tpqv/i/KTnVR0UVrnhKP9FPFrYFNEqQFq9LoXtpRZlOEE2HzfA3+Ws+ip8+JvKDAQJe+8/8Qs1aM2z8KNQtmwH1ZgJC74OLptDHVOFI4SPjAQaXoknVbYXsfogPswF0BUojx2vR7QAjhZKmb3wDY6C/yDVkdKhRzmfBT9kC1dOtH0IRpL3YSI4U9FnDp3YkKZKc1jnDUrJLOmeuh/WSth9S+XdWHTwGlqCn+7jg== x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:CO1PR11MB4929.namprd11.prod.outlook.com;PTR:;CAT:NONE;SFS:(13230028)(346002)(39860400002)(136003)(396003)(366004)(376002)(451199021)(166002)(86362001)(41300700001)(38070700005)(76236004)(7696005)(966005)(55016003)(4326008)(316002)(71200400001)(33656002)(45080400002)(66446008)(66476007)(66556008)(64756008)(66946007)(76116006)(107886003)(52536014)(5660300002)(186003)(2906002)(478600001)(53546011)(9686003)(6506007)(26005)(83380400001)(66899021)(122000001)(54906003)(8676002)(8936002)(82960400001)(110136005)(38100700002)(9326002)(1406899024);DIR:OUT;SFP:1102; x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?wIhq4dNMuefryDHNZbFupS5gQb+6bvQeTZRMPajgagilgz8XydeK8x/sTvv0?= =?us-ascii?Q?T0ZA/QOq1CSLZFfHekShN8ymNc8J4u1jJUgLKidqOJTv68HGaSJhxJPiRxij?= =?us-ascii?Q?+fXwNIBQANuA2UwTLke3ob6LPADYJwRzIuHdhhJsSVeGf/+XJv6rpUji21sw?= =?us-ascii?Q?SbrSxc3xoAepLGfCh786qNPqfXfG2BHo13TXk8vWdmJEwLA+KNJbvfcjQKz4?= =?us-ascii?Q?8xXzLqQum3zRu2uB5eRyoA5e643dRD7KCoG5fLblGDVseGDP5zyXx2Vvwq7y?= =?us-ascii?Q?vqCObsFKmySkEv/JoILHhNHwePL8pKU7hly77zYIaJwYqaAiPpvvlNTBA1FT?= =?us-ascii?Q?m27/lv5SHtQcTvWFrGdOBy8oT9iPNuZuRzJW8qvoFvwBmagVu8Odq1VzOGSl?= =?us-ascii?Q?KlV4toS32KpN68BP0f0aJK1H6RApXIUFOxIDdY1nH4X0wjkPMCuyh5dPnklQ?= =?us-ascii?Q?y46cFNW24cUQnKt1Wg9VPkzyF/8IxvUrjIvG9TUVkRU7y7NA4NvOHh8VmTgc?= =?us-ascii?Q?9uvU8XsdNpDYoUuwnHseIjakRnp6R03NNKfrZ/rQbXo2AQa1Z+EccnKPqjRD?= =?us-ascii?Q?loSZd872BJe9xJYJMBQ0eTscwx3Jmhccv0PVK+5xt0Jd/iPtB8NLvNJXEjAT?= =?us-ascii?Q?YDrvnLT9e4mgOBPiPZvpxBJVcmn11/qGIYXHSNp7B2dSCSmhjEyjdrqVQ1mL?= =?us-ascii?Q?02aXcSL1ZschQ3PFpikpoWOKffWCzdST5FWO3+XmDkHmoqUUUK6jYXoz8QNY?= =?us-ascii?Q?mbj+g72j4tBt1vQBCgaYieEOPY7L8TP5UVFiTETUJgUUvATjdrC5fLUyNUXo?= =?us-ascii?Q?b6aujKVXOZMrkx+tXjMztgtsCRgDYpMWllOyKGoSvEtMpph4jY3QeQAhLorj?= =?us-ascii?Q?NtFsHJavBL429a8uTEJ11cy84swKzycfZokTl9j2QckNLv1QWSkif9YhqhyD?= =?us-ascii?Q?FPxZjR8bpKn+djn2z/AfFZxGvcTNX1aQ7+HzAka5lftYKBA/oejirR+OgH4f?= =?us-ascii?Q?DNHAWvBWNTBMlpmZeezSwa7jWuVgbCCmi7kPnCQIR5mK0gppurbk5Z1icfCp?= =?us-ascii?Q?FwRvBrDQSDF6Cx+Q34yHwHW3H5NY3Sa8C8PSUGXLD2Gxmhdk2LnINkEBDGA+?= =?us-ascii?Q?nnOYhRYMe7c0QoH+UiyAwbXoEb+yDoSDkXMgVwbRlBuRmIcKzGanSA8Qw4qi?= =?us-ascii?Q?JnU8jk8SspZZ6ZHg2xkfxj/kTy5y3RkqcjObCubCTr2AQ1pSjPA8ueIMPPnS?= =?us-ascii?Q?nlLgmhY6JaK3dqaeRzUeAKwTeMQQqKZdSvH+mz/C9LmQ1xNLGw2QsHlmb3YZ?= =?us-ascii?Q?l/8eUAZVQQuMfi3AuNrI4bG/c4OTLg/xQp40SqmA7917uR+EDXJON2ClAO8G?= =?us-ascii?Q?6PNbNNaDgmnXN2BJZvfhHVZJxFxXT89okcYFeLjTsciGF6Nlq7ctlEAtH4kd?= =?us-ascii?Q?zTScNqRpmROnl8U9Mnv+HJyo/GLdpwLvf63oh0pvrsCMG8teSlsQGzp8wcwJ?= =?us-ascii?Q?uohFKJpHKlzd1XRmWgUDSTh4BdGEenK/IRLHZ9/1vfTzjWYjcYVOqf+oElx5?= =?us-ascii?Q?21D53KOo0k5wZETwJjQJbo6on/4iRGZLhIsoMWUD?= MIME-Version: 1.0 X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: CO1PR11MB4929.namprd11.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: 3064ddc5-0fc9-48f0-cb27-08db60640701 X-MS-Exchange-CrossTenant-originalarrivaltime: 29 May 2023 16:44:53.3439 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 46c98d88-e344-4ed4-8496-4ed7712e255d X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: LXxqO3iJvMEK7wQDWF0ymHWbmmzcMxNhiw0dxPrimw3VOajdUl3iKyvpw3hq57nGfkxpThgVyCP7mNP54WCHeEK7lRtYzkLmsRzaYzb/rvs= X-MS-Exchange-Transport-CrossTenantHeadersStamped: PH8PR11MB7144 Return-Path: michael.d.kinney@intel.com X-OriginatorOrg: intel.com Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_CO1PR11MB492965340B2B53890CF6B9B9D24A9CO1PR11MB4929namp_" --_000_CO1PR11MB492965340B2B53890CF6B9B9D24A9CO1PR11MB4929namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Sean, I see the "rerun" button on the "checks" page of GitHub from my login. We have a mix of both Azure Pipelines and GitHub Actions today, so I think = it is important to see the "rerun" from GitHub view for Maintainers. This github page describes the feature, but not the permissions required. https://docs.github.com/en/actions/managing-workflow-runs/re-running-workfl= ows-and-jobs We currently have EDK II Maintainer Team set to "Triage Role" permissions. = From the table below, only "Write" and above are allowed to re-run. https://docs.github.com/en/organizations/managing-user-access-to-your-organ= izations-repositories/repository-roles-for-an-organization#permissions-for-= each-role "Write" permissions add a lot of options, so I think we should discuss trad= eoffs in the next Tools/CI meeting. One option is to add a bot based on a new label to request failed jobs to b= e re-run. The bot can use a token with permissions to re-run. Best regards, Mike From: Sean Brogan Sent: Monday, May 29, 2023 8:37 AM To: Kinney, Michael D ; devel@edk2.groups.io; a= rdb@kernel.org; Rebecca Cran Cc: Kubacki, Michael ; Gao, Liming ; Kinney, Michael D Subject: Re: [edk2-devel] failed Pr It has changed over time and I no longer see a button on the "checks" page = of GitHub. I only see the button in the azure pipeline which would mean ma= intainers would need to be "contributors" in the azure DevOps organization/= project. I have no problem with that and it looks like you can sign in with= a GitHub account so it should just be a matter of collecting the email add= ress associated with their GitHub and inviting them to join. We only get 5= free basic users but we get unlimited free "stakeholder" accounts. I assum= e we might need basic accounts to interact with the pipeline stuff but I do= n't know for sure. Anyone who has paid Microsoft visual studio subscriptio= ns (like from an employer) usually doesn't count towards the 5. Regardless for those actively contributing and interested we should add the= m up to the limit. This was one of the reasons we had desired long term to= align on GitHub build services instead. Other thoughts? Thanks Sean ________________________________ From: Kinney, Michael D > Sent: Monday, May 29, 2023 8:13:32 AM To: devel@edk2.groups.io >; spbrogan@outlook.com >; ardb@kernel.org= >; Rebecca= Cran > Cc: Kubacki, Michael >; Gao, Liming >; Kinney, Michael D > Subject: RE: [edk2-devel] failed Pr Hi Sean, Do you know what GitHub permissions are required to see the re-run button? I think it is reasonable for all Maintainers to have that available. Mike 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 > Cc: devel@edk2.groups.io; Kinney, Michael D >; Kubacki, Mic= hael >;= Gao, Liming > Subject: Re: [edk2-devel] failed Pr It has been rerun. ________________________________ From: devel@edk2.groups.io > on behalf of Ard Biesheuvel > Sent: Monday, May 29, 2023 7:44:37 AM To: Rebecca Cran > Cc: devel@edk2.groups.io >; Michael Kinney >; Michael Kubacki >; Liming Gao (Byosoft addres= s) > Subject: Re: [edk2-devel] failed Pr 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. --_000_CO1PR11MB492965340B2B53890CF6B9B9D24A9CO1PR11MB4929namp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi Sean,

 

I see the “rerun” button on the “c= hecks” page of GitHub from my login.

 

We have a mix of both Azure Pipelines and GitHub Act= ions today, so I think it is important to see the “rerun” from = GitHub view for Maintainers.

 

This github page describes the feature, but not the = permissions required.

 

= https://docs.github.com/en/actions/managing-workflow-runs/re-running-workfl= ows-and-jobs

 

We currently have EDK II Maintainer Team set to R= 20;Triage Role” permissions.  From the table below, only “= Write” and above are allowed to re-run.

 

htt= ps://docs.github.com/en/organizations/managing-user-access-to-your-organiza= tions-repositories/repository-roles-for-an-organization#permissions-for-eac= h-role

 

“Write” permissions add a lot of options= , so I think we should discuss tradeoffs in the next Tools/CI meeting.=

 

One option is to add a bot based on a new label to r= equest failed jobs to be re-run.  The bot can use a token with permiss= ions to re-run.

 

Best regards,

 

Mike

 

From: Sean Brogan <spbrogan@outlook.com>= ;
Sent: Monday, May 29, 2023 8:37 AM
To: Kinney, Michael D <michael.d.kinney@intel.com>; devel@edk2= .groups.io; ardb@kernel.org; Rebecca Cran <rebecca@bsdio.com>
Cc: Kubacki, Michael <michael.kubacki@microsoft.com>; Gao, Lim= ing <gaoliming@byosoft.com.cn>; Kinney, Michael D <michael.d.kinne= y@intel.com>
Subject: Re: [edk2-devel] failed Pr

 

It has changed over time and I no longer see a butto= n on the "checks" page of GitHub.  I only see the button in = the azure pipeline which would mean maintainers would need to be "cont= ributors" in the azure DevOps organization/project. I have no problem with that and it looks like you can sign in with a GitHub = account so it should just be a matter of collecting the email address assoc= iated with their GitHub and inviting them to join.  We only get 5 free= basic users but we get unlimited free "stakeholder" accounts. I assume we might need basic accounts to= interact with the pipeline stuff but I don't know for sure.  Anyone w= ho has paid Microsoft visual studio subscriptions (like from an employer) u= sually doesn't count towards the 5.   

 

Regardless for those actively contributing and inter= ested we should add them up to the limit.  This was one of the reasons= we had desired long term to align on GitHub build services instead.

 

Other thoughts?

 

Thanks

Sean 

From: Kinney, Michael D <michael.d.kinney@intel.com>
Sent: Monday, May 29, 2023 8:13:32 AM
To: devel@edk2.groups.io= <devel@edk2.groups.io>; spbrogan@outlook.com <spbrogan@outlook.com>; ardb@kernel.org <ardb@kernel.org>; Rebecca Cran <rebecca@bsdio.com>
Cc: Kubacki, Michael <michael.kubacki@microsoft.com>; Gao, Liming <gaoliming@byosoft.com.cn>; Kinney, Mic= hael D <michael.d.kinney@i= ntel.com>
Subject: RE: [edk2-devel] failed Pr

 

Hi Sean,

 

Do you know what GitHub permissions are required to= see the re-run button?

 

I think it is reasonable for all Maintainers to hav= e that available.

 

Mike

 

From: devel@edk2.groups.io <deve= l@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 <= rebecca@bsdio.com>
Cc: devel@edk2.groups.io= ; Kinney, Michael D <micha= el.d.kinney@intel.com>; Kubacki, Michael <michael.kubacki@microsoft.com>; Gao, Liming <gaoliming@byos= oft.com.cn>
Subject: Re: [edk2-devel] failed Pr

 

It has been rerun. 

 

From: devel@edk2.groups.io <devel@edk2.groups.io> on behalf of= Ard Biesheuvel <ardb@kernel.org&= gt;
Sent: Monday, May 29, 2023 7:44:37 AM
To: Rebecca Cran <rebecca@bs= dio.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@bsd= io.com> wrote:
>
> It looks like the agent or machine running the CI task crashed.
>
> "##[error]We stopped hearing from agent Azure Pipelines 18. Verif= y the
> agent machine is running and has a healthy network connection. Anythin= g
> 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 cau= se
> the commit hash to change, for example by making a change to ReadMe.rs= t
> then reverting it.
>

Mike Kinney mentioned last time that there is a button I could push. Mike?<= br>
I am reluctant to make unnecessary changes to the state of the branch
just to trick the CI into having another go at it.



--_000_CO1PR11MB492965340B2B53890CF6B9B9D24A9CO1PR11MB4929namp_--