Re: [EXTERNAL] Re: [edk2-devel] Ecc style errors when running EDK2 CI locally without specifying a target (NO-TARGET)

["Laszlo Ersek" <lersek@redhat.com>]

On 10/01/20 04:25, Rebecca Cran wrote:
> Ah, thanks. I made a wrong assumption about how it works. So I can get
> it to fail faster by running "stuart_ci_build -c .pytool/CISettings.py
> TOOL_CHAIN_TAG=GCC5 -t NO-TARGET" - i.e. running NO-TARGET without also
> running DEBUG,RELEASE,NOOPT too.
> 
> 
> It turns out that because of the repo I'm running it against, where I
> haven't kept `master` up-to-date, it thinks almost all the files have
> changed - and so it runs Ecc against code that hasn't really changed for
> a long time.
> 
> "INFO - Cmd to run is: git diff --name-status HEAD origin/master"
> 
> 
> So, now I've updated my repo's `master`, it both runs much faster, and
> succeeds.

Right; a few days ago I also had to look up the "origin/master"
references in ".pytool/Plugin/EccCheck/EccCheck.py" to understand how it
restricts the warnings to "new" code. I have a dedicated VM for running
CI locally, so whenever I push a topic branch to that, I just have to
push my most recently fetched master branch reference to the VM as well.

Thanks!
Laszlo

> 
> A weekly build which runs Ecc over all the code and compiles a report of
> issues might be nice.
> 
>