From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by mx.groups.io with SMTP id smtpd.web10.216.1578334637044478357 for ; Mon, 06 Jan 2020 10:17:17 -0800 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: intel.com, ip: 192.55.52.43, mailfrom: michael.d.kinney@intel.com) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Jan 2020 10:17:16 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.69,403,1571727600"; d="scan'208";a="302947277" Received: from orsmsx104.amr.corp.intel.com ([10.22.225.131]) by orsmga001.jf.intel.com with ESMTP; 06 Jan 2020 10:17:16 -0800 Received: from orsmsx162.amr.corp.intel.com (10.22.240.85) by ORSMSX104.amr.corp.intel.com (10.22.225.131) with Microsoft SMTP Server (TLS) id 14.3.439.0; Mon, 6 Jan 2020 10:17:16 -0800 Received: from orsmsx113.amr.corp.intel.com ([169.254.9.100]) by ORSMSX162.amr.corp.intel.com ([169.254.3.178]) with mapi id 14.03.0439.000; Mon, 6 Jan 2020 10:17:15 -0800 From: "Michael D Kinney" To: Laszlo Ersek , "devel@edk2.groups.io" , Sean Brogan , "Bret Barkelew" , "Gao, Liming" , "Kinney, Michael D" Subject: Re: [edk2-devel] EDK II Maintainers - EDK II CI is now active on edk2/master Thread-Topic: [edk2-devel] EDK II Maintainers - EDK II CI is now active on edk2/master Thread-Index: AdWY/xjw4dZ1iskvSlK5J8Hop+Zpewr+ssqAAA9MzjA= Date: Mon, 6 Jan 2020 18:17:14 +0000 Message-ID: References: <1443759e-a8a1-2c5f-4892-0ff740e948ba@redhat.com> In-Reply-To: <1443759e-a8a1-2c5f-4892-0ff740e948ba@redhat.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.2.0.6 dlp-reaction: no-action x-originating-ip: [10.22.254.139] MIME-Version: 1.0 Return-Path: michael.d.kinney@intel.com Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Laszlo, Sorry for the delay in getting to these PactchCheck.py updates. I know it is frustrating to be blocked by these types of issues. I try to look at 2406 tomorrow. I think the manual override is potentially more complex to implement than the requested changed to PatchCheck.py. You were on the correct link. If you clicked one more level on "Bash exited with code '255'" link on that web page, it takes you to the patch check log that shows 3 errors for commit message subject lines being too long. https://dev.azure.com/tianocore/edk2-ci/_build/results?buildId=3D3459&view= =3Dlogs&j=3D12f1170f-54f2-53f3-20dd-22fc7dff55f9&t=3D9c939e41-62c2-5605-5e0= 5-fc3554afc9f5&l=3D149 Best regards, Mike > -----Original Message----- > From: Laszlo Ersek > Sent: Monday, January 6, 2020 9:29 AM > To: devel@edk2.groups.io; Kinney, Michael D > ; Sean Brogan > ; Bret Barkelew > ; Gao, Liming > > Subject: Re: [edk2-devel] EDK II Maintainers - EDK II > CI is now active on edk2/master >=20 > Hi Mike, >=20 > On 11/12/19 03:55, Michael D Kinney wrote: > > EDK II Maintainers, > > > > EDK II CI Phase 1 feature is now active on > edk2/master. > > > > Please use a GitHub pull request from a branch in a > personal > > fork of the edk2 repository with a 'push' label to > request > > a set of patches to be pushed to edk2/master. The > GitHub PR > > replaces the 'git push' operation currently used to > commit > > changes to edk2/master. > > > > You will need to configure your notifications from > the edk2 > > repository to make sure you receive email > notifications > > when the checks against the GitHub PR passes or > fails. > > > > If you submit a GitHub Pull Request without the > 'push' > > label, then the CI checks are run and the results are > > generated. > > > > Please let us know if there are any questions about > this > > change in the development process. >=20 > I had filed >=20 > https://bugzilla.tianocore.org/show_bug.cgi?id=3D2406 >=20 > a month ago, about PatchCheck.py being too strict, and > blocking pull requests unjustifiedly. >=20 > Now I realize I can't even review the results (=3D the > PatchCheck.py error messages) on github.com and/or on > Azure Pipelines: >=20 >=20 > https://github.com/tianocore/edk2/pull/272/checks?check > _run_id=3D375969977 > https://dev.azure.com/tianocore/11ea4a10-ac9f-4e5f- > 8b13-7def1f19d478/_build/results?buildId=3D3456 >=20 > Am I looking in the wrong place perhaps? >=20 > Can we please add a manual PatchCheck.py override on > github.com for those maintainers that are permitted to > set the "push" label already? >=20 > TianoCore#2406 doesn't seem to be getting any > attention, and it is blocking actual development work. >=20 > Thanks > Laszlo