Hi Chao,
Are you referring to the change I made to put the link to the
instructions in the build log. Here's an example of what that will look
like:
https://github.com/makubacki/tianocore.github.io/blob/temp_show_uncrustify_ci_link_in_build_log/images/edk-ii-code-formatting/temp-example-instruction-link-in-build-log.png?raw=true
(some of the words running together are not in the actual change)
I'm open to moving it elsewhere but developers will need to know how to
at least find that or they will have trouble fixing build issues.
Regards,
Michael
On 4/19/2022 9:46 PM, Chao Li wrote:
Hi Micheal,
Using the way your provided the link, I found the detail log, thanks,
but this way is not friendly to newbies, because they don't know how to
find the tutorial.:)
--
Thanks,
Chao
------------------------
On 4月 20 2022, at 7:43 早上, "Michael Kubacki"
<mikub...@linux.microsoft.com> wrote:
The wiki update is here:
https://github.com/makubacki/tianocore.github.io/blob/add_ci_uncrustify_instructions/EDK-II-Code-Formatting.md#how-to-find-uncrustify-formatting-errors-in-continuous-integration-ci
I am waiting for permissions to be updated so I can update the actual
wiki page and then I'll send a patch for the plugin change with the link
to that section.
Regards,
Michael
On 4/19/2022 6:15 PM, Michael Kubacki wrote:
> I agree that is ideal but I'm not aware of how to do that at the
moment.
>
> Thanks,
> Michael
>
> On 4/19/2022 4:52 PM, Michael D Kinney wrote:
>> Hi Michael,
>>
>> Can the build log provide a direct link to the log file artifact
if an
>> error is detected?
>>
>> Mike
>>
>>> -----Original Message-----
>>> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of
>>> Michael Kubacki
>>> Sent: Tuesday, April 19, 2022 12:42 PM
>>> To: devel@edk2.groups.io; quic_rc...@quicinc.com;
>>> spbro...@outlook.com; Chao Li <lic...@loongson.cn>
>>> Subject: Re: [edk2-devel] Some questions about Azure CI
>>>
>>> Hi Rebecca,
>>>
>>> We are trying to keep the results reporting experience
consistent with
>>> other plugins and prevent an overwhelming amount of information
being
>>> printed to the build log.
>>>
>>> In case other errors are present, providing high-level
information from
>>> each plugin can help point the user in the right direction to
get more
>>> detail.
>>>
>>> I completely understand the concern though, so I'm planning to make
>>> another step toward providing more information about how to
debug an
>>> issue, when it occurs. That is to put the step-by-step
information about
>>> where to find the file diff into the EDK II Code Formatting
wiki page
>>> and then if a failure occurs, print a link to that section of
the wiki
>>> page. I am hoping this will provide sufficient information to
get to the
>>> file diff at the point of failure.
>>>
>>> I should be able to send these patches later today.
>>>
>>> Regards,
>>> Michael
>>>
>>> On 4/19/2022 12:43 PM, Rebecca Cran wrote:
>>>> Since people are going to keep running into this, could we
just output
>>>> the file diff to the console? That would avoid having to go
hunting for
>>>> the log file.
>>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>>
Sent from Mailspring
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#89102): https://edk2.groups.io/g/devel/message/89102
Mute This Topic: https://groups.io/mt/90555787/21656
Group Owner: devel+ow...@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
