From: "Rebecca Cran" <quic_rcran@quicinc.com>
To: Michael Kubacki <mikuback@linux.microsoft.com>, <devel@edk2.groups.io>
Cc: Michael D Kinney <michael.d.kinney@intel.com>,
Liming Gao <gaoliming@byosoft.com.cn>,
Sean Brogan <sean.brogan@microsoft.com>,
Bret Barkelew <Bret.Barkelew@microsoft.com>
Subject: Re: [edk2-devel] [PATCH v1 1/1] .pytool/Plugin/UncrustifyCheck: Output file diffs by default
Date: Tue, 5 Apr 2022 08:31:35 -0600 [thread overview]
Message-ID: <788b70e7-3d38-dbd1-35a9-39eab17ac0fd@quicinc.com> (raw)
In-Reply-To: <d12c1b4f-4706-2a20-a9e5-6d434d65b832@linux.microsoft.com>
So your change in 56530dec1105f17455752675e4c90fb859c64836 didn't fix
anything, because we don't output TestSuites.xml to the console: if I
introduce a code style issue into a branch, CI still only prints the
following:
PROGRESS - --Running ArmPkg: 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/vsts/work/1/s/ArmPkg/Library/ArmSmcLib/ArmSmc.c
ERROR - --->Test Failed: Uncrustify Coding Standard Test NO-TARGET
returned 1
ERROR - Overall Build Status: Error
PROGRESS - There were 1 failures out of 13 attempts
Could we get the diff printed *there* too?
--
Rebecca Cran
On 2/25/22 14:18, Michael Kubacki wrote:
> Hi Rebecca,
>
> Sorry for the delay, I was out of office.
>
> The diff will appear in <Workspace>/Build/TestSuites.xml. Here, I have
> intentionally introduced an error in
> UnitTestFrameworkPkg\Test\UnitTest\Sample\SampleUnitTest\SampleUnitTest.c:
>
> Uncrustify executed against 21 files in UnitTestFrameworkPkg in 0.19
> seconds.
> </system-out><system-err>Files with formatting errors:
> Formatting errors in
> Test\UnitTest\Sample\SampleUnitTest\SampleUnitTest.c
> ---
> D:\src\edk2\UnitTestFrameworkPkg\Test\UnitTest\Sample\SampleUnitTest\SampleUnitTest.c
> +++
> D:\src\edk2\UnitTestFrameworkPkg\Test\UnitTest\Sample\SampleUnitTest\SampleUnitTest.c.uncrustify_plugin
> @@ -13,7 +13,7 @@
> #include <Library/UnitTestLib.h>
> #include <Library/PrintLib.h>
>
> -#define UNIT_TEST_NAME "Sample Unit Test"
> +#define UNIT_TEST_NAME "Sample Unit Test"
> #define UNIT_TEST_VERSION "0.1"
>
> ///
>
> </system-err></testcase></testsuite></testsuites>
>
> Thanks,
> Michael
>
> On 2/23/2022 12:48 PM, Rebecca Cran wrote:
>> This doesn't appear to work. If I change
>> MdeModulePkg/Bus/Pci/NvmExpressDxe/NvmExpress.c to introduce an
>> error, then I get the following output (with verbose mode):
>>
>>
>> INFO - ------------------------------------------------
>> INFO - --------------Cmd Output Finished---------------
>> INFO - --------- Running Time (mm:ss): 00:07 ----------
>> INFO - ----------- Return Code: 0x00000000 ------------
>> INFO - ------------------------------------------------
>> INFO - Uncrustify executed against 1035 files in MdeModulePkg in 7.67
>> seconds.
>>
>> INFO - Calculating file diffs. This might take a while...
>> ERROR - .../edk2/MdeModulePkg/Bus/Pci/NvmExpressDxe/NvmExpress.c
>> ERROR - --->Test Failed: Uncrustify Coding Standard Test NO-TARGET
>> returned 1
>> PROGRESS - --Running MdeModulePkg: Spell Check Test NO-TARGET --
>>
>> So it's seeing that _output_file_diffs is True, but it appears that
>> there aren't any formatted_files?
>>
>>
next prev parent reply other threads:[~2022-04-05 14:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 16:19 [PATCH v1 1/1] .pytool/Plugin/UncrustifyCheck: Output file diffs by default Michael Kubacki
2022-02-10 16:44 ` Michael D Kinney
2022-02-10 16:47 ` [edk2-devel] " Rebecca Cran
2022-02-23 17:48 ` Rebecca Cran
2022-02-25 21:18 ` Michael Kubacki
2022-04-05 14:31 ` Rebecca Cran [this message]
2022-04-05 14:46 ` Michael Kubacki
2022-04-05 14:52 ` Rebecca Cran
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=788b70e7-3d38-dbd1-35a9-39eab17ac0fd@quicinc.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