public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"quic_rcran@quicinc.com" <quic_rcran@quicinc.com>,
	"ashish.kalra@amd.com" <ashish.kalra@amd.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: Michael Kubacki <mikuback@linux.microsoft.com>
Subject: Re: [edk2-devel] EDK2 CI build error "Uncrustify Coding Standard"
Date: Tue, 5 Apr 2022 15:21:15 +0000	[thread overview]
Message-ID: <CO1PR11MB49298A1A1A422F7B4D0051EAD2E49@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <08552626-5517-0091-f7ba-a7c2db5ceff9@quicinc.com>

Hi Rebecca,

I agree this is a good way to run from command line. 

With the addition of the ignore files feature in the YAML files, you
have to make sure the filenames added to files are not in the ignored
set and not in BaseTools and not from submodules.

If you are working on a specific lib/module/pkg, then adding all the
C/H files from that scope is also a good technique.

Mike

> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Rebecca Cran
> Sent: Tuesday, April 5, 2022 8:01 AM
> To: devel@edk2.groups.io; ashish.kalra@amd.com
> Cc: Michael Kubacki <mikuback@linux.microsoft.com>
> Subject: Re: [edk2-devel] EDK2 CI build error "Uncrustify Coding Standard"
> 
> I have the following script for running Uncrustify locally on Linux:
> 
> ../edk2/.pytool/Plugin/UncrustifyCheck/mu-uncrustify-release_extdep/Linux-x86/uncrustify
> -c ../edk2/.pytool/Plugin/UncrustifyCheck/uncrustify.cfg -F files
> --replace --no-backup --if-changed
> 
> Then I just echo the paths of files I want to check/fix:
> 
> echo Platform/Qemu/SbsaQemu/OemMiscLib/OemMiscLib.c > files
> echo Silicon/Qemu/SbsaQemu/Drivers/SbsaQemuAcpiDxe/SbsaQemuAcpiDxe.c >>
> files
> 
> 
> --
> Rebecca Cran
> 
> On 4/5/22 00:09, Ashish Kalra via groups.io wrote:
> > Hi Mike,
> >
> > I am following up on Brijesh's email, i am running the CI tests
> > related to my SEV live migration patches,
> > which i am in process of posting.
> >
> > I am running the CI tests locally and getting errors while building
> > OvmfPkg, my patches include two new
> > header files, error log is copied below.
> >
> > Do you have updated instructions on how to run through uncrustify
> > locally and
> > get my patch updated with those formatting changes, especially for
> > Linux ? (your above instructions seem specific to Windows).
> >
> > Thanks,
> > Ashish
> >
> > Error log:
> >
> > ../.local/bin/stuart_ci_build -c .pytool/CISettings.py
> > TOOL_CHAIN_TAG=GCC5 -p OvmfPkg SECTION - Init SDE WARNING - Using Pip
> > Tools based BaseTools SECTION - Loading Plugins SECTION - Start
> > Invocable Tool SECTION - Getting Environment SECTION - Loading plugins
> > SECTION - Building OvmfPkg Package PROGRESS - --Running OvmfPkg:
> > Uncrustify Coding Standard Test NO-TARGET -- WARNING - A file header
> > template is not specified in the config file. WARNING - A function
> > header template is not specified in the config file. ERROR -
> > /home/amd/edk2-upstream/OvmfPkg/Library/BaseMemEncryptSevLib/PeiMemEncryptSevLibInternal.c
> > ERROR -
> > /home/amd/edk2-upstream/OvmfPkg/Library/BaseMemEncryptSevLib/DxeMemEncryptSevLibInternal.c
> > ERROR - --->Test Failed: Uncrustify Coding Standard Test NO-TARGET
> > returned 2 PROGRESS - --Running OvmfPkg: Guid Check Test NO-TARGET --
> > PROGRESS - --->Test Success: Guid Check Test NO-TARGET PROGRESS -
> > --Running OvmfPkg: Char Encoding Check Test NO-TARGET -- PROGRESS -
> > --->Test Success: Char Encoding Check Test NO-TARGET PROGRESS -
> > --Running OvmfPkg: Spell Check Test NO-TARGET -- WARNING - NodeJs not
> > installed. Test can't run WARNING - --->Test Skipped: in plugin! Spell
> > Check Test NO-TARGET PROGRESS - --Running OvmfPkg: Dsc Complete Check
> > Test NO-TARGET -- PROGRESS - --->Test Success: Dsc Complete Check Test
> > NO-TARGET PROGRESS - --Running OvmfPkg: Host Unit Test Dsc Complete
> > Check Test NO-TARGET -- PROGRESS - --->Test Success: Host Unit Test
> > Dsc Complete Check Test NO-TARGET PROGRESS - --Running OvmfPkg: Host
> > Unit Test Compiler Plugin NOOPT -- WARNING - --->Test Skipped: in
> > plugin! Host Unit Test Compiler Plugin NOOPT PROGRESS - --Running
> > OvmfPkg: Library Class Check Test NO-TARGET -- PROGRESS - --->Test
> > Success: Library Class Check Test NO-TARGET PROGRESS - --Running
> > OvmfPkg: EccCheck Test NO-TARGET -- PROGRESS - --->Test Skipped by
> > package! EccCheck Test PROGRESS - --Running OvmfPkg: Compiler Plugin
> > DEBUG -- WARNING - --->Test Skipped: in plugin! Compiler Plugin DEBUG
> > PROGRESS - --Running OvmfPkg: Compiler Plugin RELEASE -- WARNING -
> > --->Test Skipped: in plugin! Compiler Plugin RELEASE PROGRESS -
> > --Running OvmfPkg: Dependency Check Test NO-TARGET -- PROGRESS -
> > --->Test Success: Dependency Check Test NO-TARGET PROGRESS - --Running
> > OvmfPkg: License Check Test NO-TARGET -- PROGRESS - --->Test Success:
> > License Check Test NO-TARGET ERROR - Overall Build Status: Error
> > PROGRESS - There were 1 failures out of 13 attempts SECTION - Summary
> > ERROR - Error
> >
> 
> 
> 
> 
> 


      reply	other threads:[~2022-04-05 15:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-07 19:52 EDK2 CI build error "Uncrustify Coding Standard" Brijesh Singh
2021-12-07 20:49 ` [edk2-devel] " Michael Kubacki
2021-12-07 21:02   ` Michael D Kinney
2021-12-08 14:39     ` Brijesh Singh
2021-12-08 16:10       ` Brijesh Singh
2021-12-08 16:15         ` Michael Kubacki
2022-04-05  5:57           ` Ashish Kalra
2022-04-05  6:09             ` Ashish Kalra
2022-04-05 14:40               ` Michael Kubacki
2022-04-05 14:42                 ` Michael Kubacki
2022-04-05 15:00               ` Rebecca Cran
2022-04-05 15:21                 ` Michael D Kinney [this message]

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=CO1PR11MB49298A1A1A422F7B4D0051EAD2E49@CO1PR11MB4929.namprd11.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