public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Sean" <spbrogan@outlook.com>
To: devel@edk2.groups.io, gaoliming@byosoft.com.cn,
	lersek@redhat.com, 'Michael Kinney' <michael.d.kinney@intel.com>,
	'Sean Brogan' <sean.brogan@microsoft.com>,
	"'Ard Biesheuvel (ARM address)'" <ard.biesheuvel@arm.com>,
	"'Leif Lindholm (Nuvia address)'" <leif@nuviainc.com>,
	'Andrew Fish' <afish@apple.com>
Subject: Re: 回复: 回复: [edk2-devel] please let's disable the ECC plugin in CI, in its current form
Date: Wed, 9 Dec 2020 19:39:25 -0800	[thread overview]
Message-ID: <DM6PR07MB7180CF6B0D605F3096D1D819C8CB0@DM6PR07MB7180.namprd07.prod.outlook.com> (raw)
In-Reply-To: <004801d6ce94$9afef490$d0fcddb0$@byosoft.com.cn>

I have been thinking about the idea of a CI plugin type that is provided 
a file list and only operates on the supplied file list.

Then during CI execution if a file list was provided these plugins would 
run and evaluate on that file list.  In azure pipeline we already get 
the diff between target branch and PR.  We could then write that to file 
and pass that file into the stuart_ci_build process.

Anyway if you have other ideas i'll leave it to you.  Please let me know 
if you are interested, want to discuss more, or go in this direction.

Thanks
Sean


On 12/9/2020 5:34 PM, gaoliming wrote:
> Sean:
>   I will give the proposal to fix this issue https://bugzilla.tianocore.org/show_bug.cgi?id=2986. In fact, we can enhance ECC to skip the folder or files.
> 
> Thanks
> Liming
>> -----邮件原件-----
>> 发件人: Sean Brogan <spbrogan@outlook.com>
>> 发送时间: 2020年12月9日 2:37
>> 收件人: devel@edk2.groups.io; gaoliming@byosoft.com.cn;
>> lersek@redhat.com; 'Michael Kinney' <michael.d.kinney@intel.com>; 'Sean
>> Brogan' <sean.brogan@microsoft.com>; 'Ard Biesheuvel (ARM address)'
>> <ard.biesheuvel@arm.com>; 'Leif Lindholm (Nuvia address)'
>> <leif@nuviainc.com>; 'Andrew Fish' <afish@apple.com>
>> 主题: Re: 回复: [edk2-devel] please let's disable the ECC plugin in CI, in its
>> current form
>>
>> Liming
>>
>> I agree it would be great to get to a place where a package maintainer
>> could turn this on but because of this bug
>> https://bugzilla.tianocore.org/show_bug.cgi?id=2986 I think this needs
>> to be completely disabled until the above is resolved.
>>
>> Thanks
>> Sean
>>
>>
>> On 12/8/2020 7:38 AM, gaoliming wrote:
>>> Laszlo:
>>>     ECC tool is not perfect. It is still helpful. I am OK to disable ECC plugin in
>> CI. But, I request to expose the option to enable it per package. If the
>> package maintainer thinks ECC is valuable, he can enable ECC plugin in one
>> package. As MdePkg maintainer, I can help to resolve ECC issue in MdePkg
>> patch. So, I would keep ECC plugin in MdePkg.
>>>
>>> Thanks
>>> Liming
>>>> -----邮件原件-----
>>>> 发件人: bounce+27952+68414+4905953+8761045@groups.io
>>>> <bounce+27952+68414+4905953+8761045@groups.io> 代表 Laszlo
>> Ersek
>>>> 发送时间: 2020年12月8日 10:05
>>>> 收件人: Michael Kinney <michael.d.kinney@intel.com>; Sean Brogan
>>>> <sean.brogan@microsoft.com>; Ard Biesheuvel (ARM address)
>>>> <ard.biesheuvel@arm.com>; Leif Lindholm (Nuvia address)
>>>> <leif@nuviainc.com>; Andrew Fish <afish@apple.com>
>>>> 抄送: edk2-devel-groups-io <devel@edk2.groups.io>
>>>> 主题: [edk2-devel] please let's disable the ECC plugin in CI, in its current
>> form
>>>>
>>>> Hi All,
>>>>
>>>> in my opinion, the ECC plugin in CI has not been productive or helpful.
>>>> The errors it reports are not convincing, and exceptions are difficult
>>>> to add, or even express. I request that we disable ECC globally for
>>>> edk2, or at least make it controllable through a github PR flag (not
>>>> through CI metafile changes in edk2).
>>>>
>>>> (Metafile changes could be an acceptable way of controlling ECC if (a)
>>>> they didn't have to go through review, (b) if technically such changes
>>>> would take effect in CI even if they were included in the patch series
>>>> subject to the CI run. Then a maintainer could evaluate and
>>>> *immediately* suppress such ECC issues by adding the exceptions as a
>>>> prepended patch, and force-pushing the updated branch to the same open
>>>> PR. But this would remain much inferior to simply disabling ECC, or
>>>> controlling it through a PR label.)
>>>>
>>>> Thanks
>>>> Laszlo
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
> 
> 
> 
> 
> 
> 
> 

  reply	other threads:[~2020-12-10  3:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-08  2:04 please let's disable the ECC plugin in CI, in its current form Laszlo Ersek
2020-12-08  7:03 ` Ard Biesheuvel
2020-12-08 15:38 ` 回复: [edk2-devel] " gaoliming
2020-12-08 18:37   ` Sean
2020-12-10  1:34     ` 回复: " gaoliming
2020-12-10  3:39       ` Sean [this message]
2020-12-11  1:10         ` 回复: " gaoliming
     [not found]   ` <164ED1ABFE90B1B0.9298@groups.io>
2020-12-09 10:24     ` Sean
2020-12-10  8:12       ` Laszlo Ersek
2020-12-10  8:52   ` Laszlo Ersek
2020-12-11  1:13     ` 回复: " gaoliming

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=DM6PR07MB7180CF6B0D605F3096D1D819C8CB0@DM6PR07MB7180.namprd07.prod.outlook.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