Some questions about Azure CI


Chao Li
 

Hi Sean and Bret,


Question1:
The CI tells me a fail that: "Test Failed: Uncrustify Coding Standard Test NO-TARGET", I'm not sure what happens when this class failure occurs, can you tell me what happened and how to fix it?

Question2:
There are many coding style errors with ECC(like: "Variable name does not follow the rules: 1. First character should be upper case 2. Must contain lower case characters 3. No white space characters 4. Global variable name must start with a 'g', *Member variable [BASE_LIBRARY_JUMP_BUFFER.S2] NOT follow naming convention."), but I found that other architectures have the same coding style as ours, can you tell me how to fix thus coding style error?

Hope you reply, thank you very much.


--
Thanks,
Chao
------------------------



Sean
 

Q1 - There should be more details in the actual log file, but your code has formatting errors.   In the last few months, the uncrusitfy tool has been introduced to get common formatting errors fixed.   See details here: EDK II Code Formatting · tianocore/tianocore.github.io Wiki

Q2 - New code additions require passing ECC.  You will just need to work through the reported errors. 

Thanks
Sean


Rebecca Cran
 

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.

--
Rebecca Cran

On 4/19/22 10:39, Sean wrote:
Q1 - There should be more details in the actual log file, but your code has formatting errors.   In the last few months, the uncrusitfy tool has been introduced to get common formatting errors fixed.   See details here: EDK II Code Formatting · tianocore/tianocore.github.io Wiki <https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Code-Formatting>

Q2 - New code additions require passing ECC.  You will just need to work through the reported errors.

Thanks
Sean


Michael Kubacki
 

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.


Michael D Kinney
 

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_rcran@...; spbrogan@...; Chao Li <lichao@...>
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.



Michael Kubacki
 

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_rcran@...; spbrogan@...; Chao Li <lichao@...>
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.



Michael Kubacki
 

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_rcran@...; spbrogan@...; Chao Li <lichao@...>
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.






Chao Li
 

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" <mikuback@...> 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_rcran@...;
>>> spbrogan@...; Chao Li <lichao@...>
>>> 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


Michael Kubacki
 

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" <mikuback@...> 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_rcran@...;
>>> spbrogan@...; Chao Li <lichao@...>
>>> 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


Michael Kubacki
 

On 4/19/2022 7:43 PM, Michael Kubacki 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_rcran@...; spbrogan@...; Chao Li <lichao@...>
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.






Chao Li
 

Hi Micheal,

Sorry for late reply, I'm busy with other things, focusing on modifying our code, refer to the detailed error log file.

I am learning how to get the detailed log from this link:
I didn't find the detailed log link in the Azure error log, it looks like:

--
Thanks,
Chao
------------------------


On 4月 20 2022, at 9:56 上午, "Michael Kubacki" <mikuback@...> wrote:
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"
> <mikuback@...> 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_rcran@...;
> >>> spbrogan@...; Chao Li <lichao@...>
> >>> 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
Sent from Mailspring


Chao Li
 

Hi Micheal,

Do you know if anyone has modified the Azure CI today? I did a CI test today, and many modules reported errors, but yesterday, only two modules reported errors, I don't know what happened. Please refer following two links:

Today:
Yesterday:

--
Thanks,
Chao
------------------------


On 4月 20 2022, at 6:10 晚上, Chao Li <lichao@...> wrote:
Hi Micheal,

Sorry for late reply, I'm busy with other things, focusing on modifying our code, refer to the detailed error log file.

I am learning how to get the detailed log from this link:
I didn't find the detailed log link in the Azure error log, it looks like:

--
Thanks,
Chao
------------------------


On 4月 20 2022, at 9:56 上午, "Michael Kubacki" <mikuback@...> wrote:
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"
> <mikuback@...> 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_rcran@...;
> >>> spbrogan@...; Chao Li <lichao@...>
> >>> 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
Sent from Mailspring


Michael Kubacki
 

My understanding is that you were referring to the document on my fork being difficult to access and you shared a link to your CI results that does not have the message pointing to the wiki page yet.

This is all correct. The wiki content has moved from my fork to the official wiki page and the patch that adds the message to the CI results has not been merged yet. It is posted on the mailing list here and waiting for reviews:

https://edk2.groups.io/g/devel/message/89098

---

As for your build failing between yesterday and today, note that the builds are based on different commits.

Yesterday:
https://github.com/loongson/edk2/commit/8d100910a2ad98b71acaabc0dcdd70be7e0eba63

Today:
https://github.com/loongson/edk2/commit/6ca5d9d6c55ca773a652fe52508e980c7aa372d3

The commits have different content. In particular, I took a quick look at a build that is failing now (Build_GCC5 TARGET_MDEMODULE_DEBUG) but previously succeeded.

The compilation step is failing for reasons such as the following:

INFO - /home/vsts/work/1/s/MdePkg/Include/LoongArch64/ProcessorBind.h:35:24: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘UINT16’
INFO - 35 | typedef unsigned shor UINT16;

Notice, that there is a typo introduced in the new commit. "shor" versus "short", this is what is causing compilation failure.

Here is a comparison of those two commits showing the line in ProcessorBind.h that is causing the problem:

https://github.com/loongson/edk2/compare/8d10091..6ca5d9d#diff-50b24eb92c5785d5c70097a70104040fcacfb70225dd8196c1a97ef3bbb305c8R35-R36

Regards,
Michael

On 4/20/2022 7:08 AM, Chao Li wrote:
Hi Micheal,
Do you know if anyone has modified the Azure CI today? I did a CI test today, and many modules reported errors, but yesterday, only two modules reported errors, I don't know what happened. Please refer following two links:
Today:
https://dev.azure.com/kilaterlee/LoongArch_edk2/_build/results?buildId=32&view=results <https://link.getmailspring.com/link/3FB8CF0A-BF1B-4A0A-924B-3B5F6D7EB834@getmailspring.com/0?redirect=https%3A%2F%2Fdev.azure.com%2Fkilaterlee%2FLoongArch_edk2%2F_build%2Fresults%3FbuildId%3D32%26view%3Dresults&recipient=bWlrdWJhY2tAbGludXgubWljcm9zb2Z0LmNvbQ%3D%3D>
Yesterday:
https://dev.azure.com/kilaterlee/LoongArch_edk2/_build/results?buildId=31&view=results <https://link.getmailspring.com/link/3FB8CF0A-BF1B-4A0A-924B-3B5F6D7EB834@getmailspring.com/1?redirect=https%3A%2F%2Fdev.azure.com%2Fkilaterlee%2FLoongArch_edk2%2F_build%2Fresults%3FbuildId%3D31%26view%3Dresults&recipient=bWlrdWJhY2tAbGludXgubWljcm9zb2Z0LmNvbQ%3D%3D>
--
Thanks,
Chao
------------------------
On 4月 20 2022, at 6:10 晚上, Chao Li <lichao@...> wrote:
Hi Micheal,
Sorry for late reply, I'm busy with other things, focusing on
modifying our code, refer to the detailed error log file.
I am learning how to get the detailed log from this link:
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
<https://link.getmailspring.com/link/3FB8CF0A-BF1B-4A0A-924B-3B5F6D7EB834@getmailspring.com/2?redirect=https%3A%2F%2Flink.getmailspring.com%2Flink%2FCA5CE175-A392-4D5E-9BE9-392B7A97BB32%40getmailspring.com%2F0%3Fredirect%3Dhttps%253A%252F%252Fgithub.com%252Fmakubacki%252Ftianocore.github.io%252Fblob%252Fadd_ci_uncrustify_instructions%252FEDK-II-Code-Formatting.md%2523how-to-find-uncrustify-formatting-errors-in-continuous-integration-ci%26recipient%3DZGV2ZWxAZWRrMi5ncm91cHMuaW8%253D&recipient=bWlrdWJhY2tAbGludXgubWljcm9zb2Z0LmNvbQ%3D%3D>.
I didn't find the detailed log link in the Azure error log, it looks
like:
https://dev.azure.com/kilaterlee/LoongArch_edk2/_build/results?buildId=31&view=logs&j=9701361e-2546-5093-77e5-58c75d95b7ce&t=27131ef8-75e1-57c3-3236-d806181f2f1f
<https://link.getmailspring.com/link/3FB8CF0A-BF1B-4A0A-924B-3B5F6D7EB834@getmailspring.com/3?redirect=https%3A%2F%2Flink.getmailspring.com%2Flink%2FCA5CE175-A392-4D5E-9BE9-392B7A97BB32%40getmailspring.com%2F1%3Fredirect%3Dhttps%253A%252F%252Fdev.azure.com%252Fkilaterlee%252FLoongArch_edk2%252F_build%252Fresults%253FbuildId%253D31%2526view%253Dlogs%2526j%253D9701361e-2546-5093-77e5-58c75d95b7ce%2526t%253D27131ef8-75e1-57c3-3236-d806181f2f1f%26recipient%3DZGV2ZWxAZWRrMi5ncm91cHMuaW8%253D&recipient=bWlrdWJhY2tAbGludXgubWljcm9zb2Z0LmNvbQ%3D%3D>.
--
Thanks,
Chao
------------------------
On 4月 20 2022, at 9:56 上午, "Michael Kubacki"
<mikuback@...> wrote:
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"
> <mikuback@...> 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_rcran@...;
> >>> spbrogan@...; Chao Li <lichao@...>
> >>> 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
>
Sent from Mailspring


Chao Li
 

Hi Micheal,

Sorry for my so carelessness, I actually fixed our code yesterday, I think this bug was brought on by when I modified the code formatting, I will check carefully next time. Sorry again.

--
Thanks,
Chao
------------------------


On 4月 20 2022, at 10:45 晚上, "Michael Kubacki" <mikuback@...> wrote:
My understanding is that you were referring to the document on my fork
being difficult to access and you shared a link to your CI results that
does not have the message pointing to the wiki page yet.

This is all correct. The wiki content has moved from my fork to the
official wiki page and the patch that adds the message to the CI results
has not been merged yet. It is posted on the mailing list here and
waiting for reviews:

https://edk2.groups.io/g/devel/message/89098

---

As for your build failing between yesterday and today, note that the
builds are based on different commits.

Yesterday:
https://github.com/loongson/edk2/commit/8d100910a2ad98b71acaabc0dcdd70be7e0eba63

Today:
https://github.com/loongson/edk2/commit/6ca5d9d6c55ca773a652fe52508e980c7aa372d3

The commits have different content. In particular, I took a quick look
at a build that is failing now (Build_GCC5 TARGET_MDEMODULE_DEBUG) but
previously succeeded.

The compilation step is failing for reasons such as the following:

INFO -
/home/vsts/work/1/s/MdePkg/Include/LoongArch64/ProcessorBind.h:35:24:
error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘UINT16’
INFO - 35 | typedef unsigned shor UINT16;

Notice, that there is a typo introduced in the new commit. "shor" versus
"short", this is what is causing compilation failure.

Here is a comparison of those two commits showing the line in
ProcessorBind.h that is causing the problem:

https://github.com/loongson/edk2/compare/8d10091..6ca5d9d#diff-50b24eb92c5785d5c70097a70104040fcacfb70225dd8196c1a97ef3bbb305c8R35-R36

Regards,
Michael

On 4/20/2022 7:08 AM, Chao Li wrote:
> Hi Micheal,
>
> Do you know if anyone has modified the Azure CI today? I did a CI test
> today, and many modules reported errors, but yesterday, only two modules
> reported errors, I don't know what happened. Please refer following two
> links:
>
> Today:
> https://dev.azure.com/kilaterlee/LoongArch_edk2/_build/results?buildId=32&view=results
> <https://link.getmailspring.com/link/3FB8CF0A-BF1B-4A0A-924B-3B5F6D7EB834@.../0?redirect=https%3A%2F%2Fdev.azure.com%2Fkilaterlee%2FLoongArch_edk2%2F_build%2Fresults%3FbuildId%3D32%26view%3Dresults&recipient=bWlrdWJhY2tAbGludXgubWljcm9zb2Z0LmNvbQ%3D%3D>
> Yesterday:
> https://dev.azure.com/kilaterlee/LoongArch_edk2/_build/results?buildId=31&view=results
> <https://link.getmailspring.com/link/3FB8CF0A-BF1B-4A0A-924B-3B5F6D7EB834@.../1?redirect=https%3A%2F%2Fdev.azure.com%2Fkilaterlee%2FLoongArch_edk2%2F_build%2Fresults%3FbuildId%3D31%26view%3Dresults&recipient=bWlrdWJhY2tAbGludXgubWljcm9zb2Z0LmNvbQ%3D%3D>
>
> --
> Thanks,
> Chao
> ------------------------
>
>
> On 4月 20 2022, at 6:10 晚上, Chao Li <lichao@...> wrote:
>
> Hi Micheal,
>
> Sorry for late reply, I'm busy with other things, focusing on
> modifying our code, refer to the detailed error log file.
>
> I am learning how to get the detailed log from this link:
> 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
> <https://link.getmailspring.com/link/3FB8CF0A-BF1B-4A0A-924B-3B5F6D7EB834@.../2?redirect=https%3A%2F%2Flink.getmailspring.com%2Flink%2FCA5CE175-A392-4D5E-9BE9-392B7A97BB32%40getmailspring.com%2F0%3Fredirect%3Dhttps%253A%252F%252Fgithub.com%252Fmakubacki%252Ftianocore.github.io%252Fblob%252Fadd_ci_uncrustify_instructions%252FEDK-II-Code-Formatting.md%2523how-to-find-uncrustify-formatting-errors-in-continuous-integration-ci%26recipient%3DZGV2ZWxAZWRrMi5ncm91cHMuaW8%253D&recipient=bWlrdWJhY2tAbGludXgubWljcm9zb2Z0LmNvbQ%3D%3D>.
> I didn't find the detailed log link in the Azure error log, it looks
> like:
> https://dev.azure.com/kilaterlee/LoongArch_edk2/_build/results?buildId=31&view=logs&j=9701361e-2546-5093-77e5-58c75d95b7ce&t=27131ef8-75e1-57c3-3236-d806181f2f1f
> <https://link.getmailspring.com/link/3FB8CF0A-BF1B-4A0A-924B-3B5F6D7EB834@.../3?redirect=https%3A%2F%2Flink.getmailspring.com%2Flink%2FCA5CE175-A392-4D5E-9BE9-392B7A97BB32%40getmailspring.com%2F1%3Fredirect%3Dhttps%253A%252F%252Fdev.azure.com%252Fkilaterlee%252FLoongArch_edk2%252F_build%252Fresults%253FbuildId%253D31%2526view%253Dlogs%2526j%253D9701361e-2546-5093-77e5-58c75d95b7ce%2526t%253D27131ef8-75e1-57c3-3236-d806181f2f1f%26recipient%3DZGV2ZWxAZWRrMi5ncm91cHMuaW8%253D&recipient=bWlrdWJhY2tAbGludXgubWljcm9zb2Z0LmNvbQ%3D%3D>.
>
> --
> Thanks,
> Chao
> ------------------------
>
>
> On 4月 20 2022, at 9:56 上午, "Michael Kubacki"
> <mikuback@...> wrote:
>
> 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"
> > <mikuback@...> 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_rcran@...;
> > >>> spbrogan@...; Chao Li <lichao@...>
> > >>> 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
>
> Sent from Mailspring
Sent from Mailspring


Chao Li
 

Hi All,

There have one last error about EFI coding style error when buiding the package for MdePkg, all errors are register defined. Refer URL: https://dev.azure.com/kilaterlee/LoongArch_edk2/_build/results?buildId=42&view=logs&j=39eb2cd7-22b4-5bd2-0a69-7cfb110ec9ce&t=05ebc774-447e-5082-7d78-51b7641489fd&l=511


Such errors come from adding new ARCH support, and Liming has suggested that we update the field ExceptionList in MdePkg.ci.yaml to skip this issue. I tried it and it passed, but I don't think it is best way.


Question:

Do you or other maintainer know why other ARCH don't need to do this? If there is another way, we will try it. Please help me!


Thanks,

Chao



-----原始邮件-----
发件人:"Chao Li" <lichao@...>
发送时间:2022-04-21 09:34:51 (星期四)
收件人: "devel@edk2.groups.io" <devel@edk2.groups.io>, "mikuback@..." <mikuback@...>
抄送: "\"devel@edk2.groups.io\"" <devel@edk2.groups.io>, "\"michael.d.kinney@...\"" <michael.d.kinney@...>, "\"quic_rcran@...\"" <quic_rcran@...>, "\"spbrogan@...\"" <spbrogan@...>
主题: Re: [edk2-devel] Some questions about Azure CI

Hi Micheal,

Sorry for my so carelessness, I actually fixed our code yesterday, I think this bug was brought on by when I modified the code formatting, I will check carefully next time. Sorry again.

--
Thanks,
Chao
------------------------


On 4月 20 2022, at 10:45 晚上, "Michael Kubacki" <mikuback@...> wrote:
My understanding is that you were referring to the document on my fork
being difficult to access and you shared a link to your CI results that
does not have the message pointing to the wiki page yet.

This is all correct. The wiki content has moved from my fork to the
official wiki page and the patch that adds the message to the CI results
has not been merged yet. It is posted on the mailing list here and
waiting for reviews:

https://edk2.groups.io/g/devel/message/89098

---

As for your build failing between yesterday and today, note that the
builds are based on different commits.

Yesterday:
https://github.com/loongson/edk2/commit/8d100910a2ad98b71acaabc0dcdd70be7e0eba63

Today:
https://github.com/loongson/edk2/commit/6ca5d9d6c55ca773a652fe52508e980c7aa372d3

The commits have different content. In particular, I took a quick look
at a build that is failing now (Build_GCC5 TARGET_MDEMODULE_DEBUG) but
previously succeeded.

The compilation step is failing for reasons such as the following:

INFO -
/home/vsts/work/1/s/MdePkg/Include/LoongArch64/ProcessorBind.h:35:24:
error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘UINT16’
INFO - 35 | typedef unsigned shor UINT16;

Notice, that there is a typo introduced in the new commit. "shor" versus
"short", this is what is causing compilation failure.

Here is a comparison of those two commits showing the line in
ProcessorBind.h that is causing the problem:

https://github.com/loongson/edk2/compare/8d10091..6ca5d9d#diff-50b24eb92c5785d5c70097a70104040fcacfb70225dd8196c1a97ef3bbb305c8R35-R36

Regards,
Michael

On 4/20/2022 7:08 AM, Chao Li wrote:
> Hi Micheal,
>
> Do you know if anyone has modified the Azure CI today? I did a CI test
> today, and many modules reported errors, but yesterday, only two modules
> reported errors, I don't know what happened. Please refer following two
> links:
>
> Today:
> https://dev.azure.com/kilaterlee/LoongArch_edk2/_build/results?buildId=32&view=results
> <https://link.getmailspring.com/link/3FB8CF0A-BF1B-4A0A-924B-3B5F6D7EB834@.../0?redirect=https%3A%2F%2Fdev.azure.com%2Fkilaterlee%2FLoongArch_edk2%2F_build%2Fresults%3FbuildId%3D32%26view%3Dresults&recipient=bWlrdWJhY2tAbGludXgubWljcm9zb2Z0LmNvbQ%3D%3D>
> Yesterday:
> https://dev.azure.com/kilaterlee/LoongArch_edk2/_build/results?buildId=31&view=results
> <https://link.getmailspring.com/link/3FB8CF0A-BF1B-4A0A-924B-3B5F6D7EB834@.../1?redirect=https%3A%2F%2Fdev.azure.com%2Fkilaterlee%2FLoongArch_edk2%2F_build%2Fresults%3FbuildId%3D31%26view%3Dresults&recipient=bWlrdWJhY2tAbGludXgubWljcm9zb2Z0LmNvbQ%3D%3D>
>
> --
> Thanks,
> Chao
> ------------------------
>
>
> On 4月 20 2022, at 6:10 晚上, Chao Li <lichao@...> wrote:
>
> Hi Micheal,
>
> Sorry for late reply, I'm busy with other things, focusing on
> modifying our code, refer to the detailed error log file.
>
> I am learning how to get the detailed log from this link:
> 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
> <https://link.getmailspring.com/link/3FB8CF0A-BF1B-4A0A-924B-3B5F6D7EB834@.../2?redirect=https%3A%2F%2Flink.getmailspring.com%2Flink%2FCA5CE175-A392-4D5E-9BE9-392B7A97BB32%40getmailspring.com%2F0%3Fredirect%3Dhttps%253A%252F%252Fgithub.com%252Fmakubacki%252Ftianocore.github.io%252Fblob%252Fadd_ci_uncrustify_instructions%252FEDK-II-Code-Formatting.md%2523how-to-find-uncrustify-formatting-errors-in-continuous-integration-ci%26recipient%3DZGV2ZWxAZWRrMi5ncm91cHMuaW8%253D&recipient=bWlrdWJhY2tAbGludXgubWljcm9zb2Z0LmNvbQ%3D%3D>.
> I didn't find the detailed log link in the Azure error log, it looks
> like:
> https://dev.azure.com/kilaterlee/LoongArch_edk2/_build/results?buildId=31&view=logs&j=9701361e-2546-5093-77e5-58c75d95b7ce&t=27131ef8-75e1-57c3-3236-d806181f2f1f
> <https://link.getmailspring.com/link/3FB8CF0A-BF1B-4A0A-924B-3B5F6D7EB834@.../3?redirect=https%3A%2F%2Flink.getmailspring.com%2Flink%2FCA5CE175-A392-4D5E-9BE9-392B7A97BB32%40getmailspring.com%2F1%3Fredirect%3Dhttps%253A%252F%252Fdev.azure.com%252Fkilaterlee%252FLoongArch_edk2%252F_build%252Fresults%253FbuildId%253D31%2526view%253Dlogs%2526j%253D9701361e-2546-5093-77e5-58c75d95b7ce%2526t%253D27131ef8-75e1-57c3-3236-d806181f2f1f%26recipient%3DZGV2ZWxAZWRrMi5ncm91cHMuaW8%253D&recipient=bWlrdWJhY2tAbGludXgubWljcm9zb2Z0LmNvbQ%3D%3D>.
>
> --
> Thanks,
> Chao
> ------------------------
>
>
> On 4月 20 2022, at 9:56 上午, "Michael Kubacki"
> <mikuback@...> wrote:
>
> 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"
> > <mikuback@...> 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_rcran@...;
> > >>> spbrogan@...; Chao Li <lichao@...>
> > >>> 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
>
> Sent from Mailspring
Sent from Mailspring


本邮件及其附件含有龙芯中科的商业秘密信息,仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制或散发)本邮件及其附件中的信息。如果您错收本邮件,请您立即电话或邮件通知发件人并删除本邮件。 
This email and its attachments contain confidential information from Loongson Technology , which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this email in error, please notify the sender by phone or email immediately and delete it. 


Michael Kubacki
 

I added some contacts that might know more about what ECC requires in this case. I didn't see any obvious issues in a few of the snippets reported.

Regards,
Michael

On 5/16/2022 1:15 AM, Chao Li wrote:
Hi All,
There have one last error about EFI coding style error when buiding the package for MdePkg, all errors are register defined. Refer URL: https://dev.azure.com/kilaterlee/LoongArch_edk2/_build/results?buildId=42&view=logs&j=39eb2cd7-22b4-5bd2-0a69-7cfb110ec9ce&t=05ebc774-447e-5082-7d78-51b7641489fd&l=511 Such errors come from adding new ARCH support, and Liming has suggested that we update the field ExceptionList in MdePkg.ci.yaml to skip this issue. I tried it and it passed, but I don't think it is best way.
Question:
Do you or other maintainer know why other ARCH don't need to do this? If there is another way, we will try it. Please help me!
Thanks,
Chao
-----原始邮件-----
*发件人:*"Chao Li" <lichao@...>
*发送时间:*2022-04-21 09:34:51 (星期四)
*收件人:* "devel@edk2.groups.io" <devel@edk2.groups.io>,
"mikuback@..." <mikuback@...>
*抄送:* "\"devel@edk2.groups.io\"" <devel@edk2.groups.io>,
"\"michael.d.kinney@...\"" <michael.d.kinney@...>,
"\"quic_rcran@...\"" <quic_rcran@...>,
"\"spbrogan@...\"" <spbrogan@...>
*主题:* Re: [edk2-devel] Some questions about Azure CI
Hi Micheal,
Sorry for my so carelessness, I actually fixed our code yesterday, I
think this bug was brought on by when I modified the code
formatting, I will check carefully next time. Sorry again.
--
Thanks,
Chao
------------------------
On 4月 20 2022, at 10:45 晚上, "Michael Kubacki"
<mikuback@...> wrote:
My understanding is that you were referring to the document on
my fork
being difficult to access and you shared a link to your CI
results that
does not have the message pointing to the wiki page yet.
This is all correct. The wiki content has moved from my fork to the
official wiki page and the patch that adds the message to the CI
results
has not been merged yet. It is posted on the mailing list here and
waiting for reviews:
https://edk2.groups.io/g/devel/message/89098
---
As for your build failing between yesterday and today, note that
the
builds are based on different commits.
Yesterday:
https://github.com/loongson/edk2/commit/8d100910a2ad98b71acaabc0dcdd70be7e0eba63
Today:
https://github.com/loongson/edk2/commit/6ca5d9d6c55ca773a652fe52508e980c7aa372d3
The commits have different content. In particular, I took a
quick look
at a build that is failing now (Build_GCC5
TARGET_MDEMODULE_DEBUG) but
previously succeeded.
The compilation step is failing for reasons such as the following:
INFO -
/home/vsts/work/1/s/MdePkg/Include/LoongArch64/ProcessorBind.h:35:24:
error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before
‘UINT16’
INFO - 35 | typedef unsigned shor UINT16;
Notice, that there is a typo introduced in the new commit.
"shor" versus
"short", this is what is causing compilation failure.
Here is a comparison of those two commits showing the line in
ProcessorBind.h that is causing the problem:
https://github.com/loongson/edk2/compare/8d10091..6ca5d9d#diff-50b24eb92c5785d5c70097a70104040fcacfb70225dd8196c1a97ef3bbb305c8R35-R36
Regards,
Michael
On 4/20/2022 7:08 AM, Chao Li wrote:
> Hi Micheal,
>
> Do you know if anyone has modified the Azure CI today? I did
a CI test
> today, and many modules reported errors, but yesterday, only
two modules
> reported errors, I don't know what happened. Please refer
following two
> links:
>
> Today:
>
https://dev.azure.com/kilaterlee/LoongArch_edk2/_build/results?buildId=32&view=results

>
<https://link.getmailspring.com/link/3FB8CF0A-BF1B-4A0A-924B-3B5F6D7EB834@getmailspring.com/0?redirect=https%3A%2F%2Fdev.azure.com%2Fkilaterlee%2FLoongArch_edk2%2F_build%2Fresults%3FbuildId%3D32%26view%3Dresults&recipient=bWlrdWJhY2tAbGludXgubWljcm9zb2Z0LmNvbQ%3D%3D>

> Yesterday:
>
https://dev.azure.com/kilaterlee/LoongArch_edk2/_build/results?buildId=31&view=results

>
<https://link.getmailspring.com/link/3FB8CF0A-BF1B-4A0A-924B-3B5F6D7EB834@getmailspring.com/1?redirect=https%3A%2F%2Fdev.azure.com%2Fkilaterlee%2FLoongArch_edk2%2F_build%2Fresults%3FbuildId%3D31%26view%3Dresults&recipient=bWlrdWJhY2tAbGludXgubWljcm9zb2Z0LmNvbQ%3D%3D>

>
> --
> Thanks,
> Chao
> ------------------------
>
>
> On 4月 20 2022, at 6:10 晚上, Chao Li <lichao@...>
wrote:
>
> Hi Micheal,
>
> Sorry for late reply, I'm busy with other things, focusing on
> modifying our code, refer to the detailed error log file.
>
> I am learning how to get the detailed log from this link:
>
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

>
<https://link.getmailspring.com/link/3FB8CF0A-BF1B-4A0A-924B-3B5F6D7EB834@getmailspring.com/2?redirect=https%3A%2F%2Flink.getmailspring.com%2Flink%2FCA5CE175-A392-4D5E-9BE9-392B7A97BB32%40getmailspring.com%2F0%3Fredirect%3Dhttps%253A%252F%252Fgithub.com%252Fmakubacki%252Ftianocore.github.io%252Fblob%252Fadd_ci_uncrustify_instructions%252FEDK-II-Code-Formatting.md%2523how-to-find-uncrustify-formatting-errors-in-continuous-integration-ci%26recipient%3DZGV2ZWxAZWRrMi5ncm91cHMuaW8%253D&recipient=bWlrdWJhY2tAbGludXgubWljcm9zb2Z0LmNvbQ%3D%3D>.

> I didn't find the detailed log link in the Azure error log,
it looks
> like:
>
https://dev.azure.com/kilaterlee/LoongArch_edk2/_build/results?buildId=31&view=logs&j=9701361e-2546-5093-77e5-58c75d95b7ce&t=27131ef8-75e1-57c3-3236-d806181f2f1f

>
<https://link.getmailspring.com/link/3FB8CF0A-BF1B-4A0A-924B-3B5F6D7EB834@getmailspring.com/3?redirect=https%3A%2F%2Flink.getmailspring.com%2Flink%2FCA5CE175-A392-4D5E-9BE9-392B7A97BB32%40getmailspring.com%2F1%3Fredirect%3Dhttps%253A%252F%252Fdev.azure.com%252Fkilaterlee%252FLoongArch_edk2%252F_build%252Fresults%253FbuildId%253D31%2526view%253Dlogs%2526j%253D9701361e-2546-5093-77e5-58c75d95b7ce%2526t%253D27131ef8-75e1-57c3-3236-d806181f2f1f%26recipient%3DZGV2ZWxAZWRrMi5ncm91cHMuaW8%253D&recipient=bWlrdWJhY2tAbGludXgubWljcm9zb2Z0LmNvbQ%3D%3D>.

>
> --
> Thanks,
> Chao
> ------------------------
>
>
> On 4月 20 2022, at 9:56 上午, "Michael Kubacki"
> <mikuback@...> wrote:
>
> 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"
> > <mikuback@...> 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_rcran@...;
> > >>> spbrogan@...; Chao Li <lichao@...>
> > >>> 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
>
> Sent from Mailspring
Sent from Mailspring /本邮件及其附件含有龙芯中科的商业秘密信息,仅限于发送给上面地址中列出的 个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、 复制或散发)本邮件及其附件中的信息。如果您错收本邮件,请您立即电话或邮件 通知发件人并删除本邮件。
This email and its attachments contain confidential information from Loongson Technology , which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this email in error, please notify the sender by phone or email immediately and delete it. /


Chao Li
 

Hi All,
Are you still following this issue? I have been waiting for the best way, thank you!

Thanks,
Chao



&gt; -----原始邮件-----
&gt; 发件人: "Michael Kubacki" <mikuback@...>
&gt; 发送时间: 2022-05-17 00:12:51 (星期二)
&gt; 收件人: devel@edk2.groups.io, lichao@..., "Shenglei Zhang" <shenglei.zhang@...>, "Bob Feng" <bob.c.feng@...>
&gt; 抄送: "michael.d.kinney@..." <michael.d.kinney@...>, "quic_rcran@..." <quic_rcran@...>, "spbrogan@..." <spbrogan@...>, gaoliming@...
&gt; 主题: Re: [edk2-devel] Some questions about Azure CI
&gt;
&gt; I added some contacts that might know more about what ECC requires in
&gt; this case. I didn't see any obvious issues in a few of the snippets
&gt; reported.
&gt;
&gt; Regards,
&gt; Michael
&gt;
&gt; On 5/16/2022 1:15 AM, Chao Li wrote:
&gt; &gt; Hi All,
&gt; &gt;
&gt; &gt; There have one last error about EFI coding style error when buiding the
&gt; &gt; package for MdePkg, all errors are register defined.&nbsp;Refer
&gt; &gt; URL:&nbsp;https://dev.azure.com/kilaterlee/LoongArch_edk2/_build/results?buildId=42&;view=logs&amp;j=39eb2cd7-22b4-5bd2-0a69-7cfb110ec9ce&amp;t=05ebc774-447e-5082-7d78-51b7641489fd&amp;l=511
&gt; &gt;
&gt; &gt;
&gt; &gt;
&gt; &gt; Such errors&nbsp;come from adding new ARCH support, and&nbsp;Liming has suggested
&gt; &gt; that we&nbsp;update the field ExceptionList in MdePkg.ci.yaml to skip this
&gt; &gt; issue. I tried it and it&nbsp;passed, but I don't think it is&nbsp;best way.
&gt; &gt;
&gt; &gt;
&gt; &gt; Question:
&gt; &gt;
&gt; &gt; Do you or&nbsp;other maintainer know why other ARCH don't&nbsp;need to do this? If
&gt; &gt; there is another way, we will try it. Please help me!
&gt; &gt;
&gt; &gt;
&gt; &gt; Thanks,
&gt; &gt;
&gt; &gt; Chao
&gt; &gt;
&gt; &gt;
&gt; &gt;
&gt; &gt; -----原始邮件-----
&gt; &gt; *发件人:*"Chao Li" <lichao@...>
&gt; &gt; *发送时间:*2022-04-21 09:34:51 (星期四)
&gt; &gt; *收件人:* "devel@edk2.groups.io" <devel@edk2.groups.io>,
&gt; &gt; "mikuback@..." <mikuback@...>
&gt; &gt; *抄送:* "\"devel@edk2.groups.io\"" <devel@edk2.groups.io>,
&gt; &gt; "\"michael.d.kinney@...\"" <michael.d.kinney@...>,
&gt; &gt; "\"quic_rcran@...\"" <quic_rcran@...>,
&gt; &gt; "\"spbrogan@...\"" <spbrogan@...>
&gt; &gt; *主题:* Re: [edk2-devel] Some questions about Azure CI
&gt; &gt;
&gt; &gt; Hi Micheal,
&gt; &gt;
&gt; &gt; Sorry for my so carelessness, I actually fixed our code yesterday, I
&gt; &gt; think this bug was brought on by when I modified the code
&gt; &gt; formatting, I will check carefully next time. Sorry again.
&gt; &gt;
&gt; &gt; --
&gt; &gt; Thanks,
&gt; &gt; Chao
&gt; &gt; ------------------------
&gt; &gt;
&gt; &gt;
&gt; &gt; On 4月 20 2022, at 10:45 晚上, "Michael Kubacki"
&gt; &gt; <mikuback@...> wrote:
&gt; &gt;
&gt; &gt; My understanding is that you were referring to the document on
&gt; &gt; my fork
&gt; &gt; being difficult to access and you shared a link to your CI
&gt; &gt; results that
&gt; &gt; does not have the message pointing to the wiki page yet.
&gt; &gt;
&gt; &gt; This is all correct. The wiki content has moved from my fork to the
&gt; &gt; official wiki page and the patch that adds the message to the CI
&gt; &gt; results
&gt; &gt; has not been merged yet. It is posted on the mailing list here and
&gt; &gt; waiting for reviews:
&gt; &gt;
&gt; &gt; https://edk2.groups.io/g/devel/message/89098
&gt; &gt;
&gt; &gt; ---
&gt; &gt;
&gt; &gt; As for your build failing between yesterday and today, note that
&gt; &gt; the
&gt; &gt; builds are based on different commits.
&gt; &gt;
&gt; &gt; Yesterday:
&gt; &gt; https://github.com/loongson/edk2/commit/8d100910a2ad98b71acaabc0dcdd70be7e0eba63
&gt; &gt;
&gt; &gt;
&gt; &gt; Today:
&gt; &gt; https://github.com/loongson/edk2/commit/6ca5d9d6c55ca773a652fe52508e980c7aa372d3
&gt; &gt;
&gt; &gt;
&gt; &gt; The commits have different content. In particular, I took a
&gt; &gt; quick look
&gt; &gt; at a build that is failing now (Build_GCC5
&gt; &gt; TARGET_MDEMODULE_DEBUG) but
&gt; &gt; previously succeeded.
&gt; &gt;
&gt; &gt; The compilation step is failing for reasons such as the following:
&gt; &gt;
&gt; &gt; INFO -
&gt; &gt; /home/vsts/work/1/s/MdePkg/Include/LoongArch64/ProcessorBind.h:35:24:
&gt; &gt;
&gt; &gt; error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before
&gt; &gt; ‘UINT16’
&gt; &gt; INFO - 35 | typedef unsigned shor UINT16;
&gt; &gt;
&gt; &gt; Notice, that there is a typo introduced in the new commit.
&gt; &gt; "shor" versus
&gt; &gt; "short", this is what is causing compilation failure.
&gt; &gt;
&gt; &gt; Here is a comparison of those two commits showing the line in
&gt; &gt; ProcessorBind.h that is causing the problem:
&gt; &gt;
&gt; &gt; https://github.com/loongson/edk2/compare/8d10091..6ca5d9d#diff-50b24eb92c5785d5c70097a70104040fcacfb70225dd8196c1a97ef3bbb305c8R35-R36
&gt; &gt;
&gt; &gt;
&gt; &gt; Regards,
&gt; &gt; Michael
&gt; &gt;
&gt; &gt; On 4/20/2022 7:08 AM, Chao Li wrote:
&gt; &gt; &gt; Hi Micheal,
&gt; &gt; &gt;
&gt; &gt; &gt; Do you know if anyone has modified the Azure CI today? I did
&gt; &gt; a CI test
&gt; &gt; &gt; today, and many modules reported errors, but yesterday, only
&gt; &gt; two modules
&gt; &gt; &gt; reported errors, I don't know what happened. Please refer
&gt; &gt; following two
&gt; &gt; &gt; links:
&gt; &gt; &gt;
&gt; &gt; &gt; Today:
&gt; &gt; &gt;
&gt; &gt; https://dev.azure.com/kilaterlee/LoongArch_edk2/_build/results?buildId=32&;view=results
&gt; &gt;
&gt; &gt; &gt;
&gt; &gt; <https: link.getmailspring.com="" link="" 3fb8cf0a-bf1b-4a0a-924b-3b5f6d7eb834@...="" 0?redirect="https%3A%2F%2Fdev.azure.com%2Fkilaterlee%2FLoongArch_edk2%2F_build%2Fresults%3FbuildId%3D32%26view%3Dresults&amp;recipient=bWlrdWJhY2tAbGludXgubWljcm9zb2Z0LmNvbQ%3D%3D">
&gt; &gt;
&gt; &gt; &gt; Yesterday:
&gt; &gt; &gt;
&gt; &gt; https://dev.azure.com/kilaterlee/LoongArch_edk2/_build/results?buildId=31&;view=results
&gt; &gt;
&gt; &gt; &gt;
&gt; &gt; <https: link.getmailspring.com="" link="" 3fb8cf0a-bf1b-4a0a-924b-3b5f6d7eb834@...="" 1?redirect="https%3A%2F%2Fdev.azure.com%2Fkilaterlee%2FLoongArch_edk2%2F_build%2Fresults%3FbuildId%3D31%26view%3Dresults&amp;recipient=bWlrdWJhY2tAbGludXgubWljcm9zb2Z0LmNvbQ%3D%3D">
&gt; &gt;
&gt; &gt; &gt;
&gt; &gt; &gt; --
&gt; &gt; &gt; Thanks,
&gt; &gt; &gt; Chao
&gt; &gt; &gt; ------------------------
&gt; &gt; &gt;
&gt; &gt; &gt;
&gt; &gt; &gt; On 4月 20 2022, at 6:10 晚上, Chao Li <lichao@...>
&gt; &gt; wrote:
&gt; &gt; &gt;
&gt; &gt; &gt; Hi Micheal,
&gt; &gt; &gt;
&gt; &gt; &gt; Sorry for late reply, I'm busy with other things, focusing on
&gt; &gt; &gt; modifying our code, refer to the detailed error log file.
&gt; &gt; &gt;
&gt; &gt; &gt; I am learning how to get the detailed log from this link:
&gt; &gt; &gt;
&gt; &gt; 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
&gt; &gt;
&gt; &gt; &gt;
&gt; &gt; <https: link.getmailspring.com="" link="" 3fb8cf0a-bf1b-4a0a-924b-3b5f6d7eb834@...="" 2?redirect="https%3A%2F%2Flink.getmailspring.com%2Flink%2FCA5CE175-A392-4D5E-9BE9-392B7A97BB32%40getmailspring.com%2F0%3Fredirect%3Dhttps%253A%252F%252Fgithub.com%252Fmakubacki%252Ftianocore.github.io%252Fblob%252Fadd_ci_uncrustify_instructions%252FEDK-II-Code-Formatting.md%2523how-to-find-uncrustify-formatting-errors-in-continuous-integration-ci%26recipient%3DZGV2ZWxAZWRrMi5ncm91cHMuaW8%253D&amp;recipient=bWlrdWJhY2tAbGludXgubWljcm9zb2Z0LmNvbQ%3D%3D">.
&gt; &gt;
&gt; &gt; &gt; I didn't find the detailed log link in the Azure error log,
&gt; &gt; it looks
&gt; &gt; &gt; like:
&gt; &gt; &gt;
&gt; &gt; https://dev.azure.com/kilaterlee/LoongArch_edk2/_build/results?buildId=31&;view=logs&amp;j=9701361e-2546-5093-77e5-58c75d95b7ce&amp;t=27131ef8-75e1-57c3-3236-d806181f2f1f
&gt; &gt;
&gt; &gt; &gt;
&gt; &gt; <https: link.getmailspring.com="" link="" 3fb8cf0a-bf1b-4a0a-924b-3b5f6d7eb834@...="" 3?redirect="https%3A%2F%2Flink.getmailspring.com%2Flink%2FCA5CE175-A392-4D5E-9BE9-392B7A97BB32%40getmailspring.com%2F1%3Fredirect%3Dhttps%253A%252F%252Fdev.azure.com%252Fkilaterlee%252FLoongArch_edk2%252F_build%252Fresults%253FbuildId%253D31%2526view%253Dlogs%2526j%253D9701361e-2546-5093-77e5-58c75d95b7ce%2526t%253D27131ef8-75e1-57c3-3236-d806181f2f1f%26recipient%3DZGV2ZWxAZWRrMi5ncm91cHMuaW8%253D&amp;recipient=bWlrdWJhY2tAbGludXgubWljcm9zb2Z0LmNvbQ%3D%3D">.
&gt; &gt;
&gt; &gt; &gt;
&gt; &gt; &gt; --
&gt; &gt; &gt; Thanks,
&gt; &gt; &gt; Chao
&gt; &gt; &gt; ------------------------
&gt; &gt; &gt;
&gt; &gt; &gt;
&gt; &gt; &gt; On 4月 20 2022, at 9:56 上午, "Michael Kubacki"
&gt; &gt; &gt; <mikuback@...> wrote:
&gt; &gt; &gt;
&gt; &gt; &gt; Hi Chao,
&gt; &gt; &gt;
&gt; &gt; &gt; Are you referring to the change I made to put the link to the
&gt; &gt; &gt; instructions in the build log. Here's an example of what that
&gt; &gt; &gt; will look
&gt; &gt; &gt; like:
&gt; &gt; &gt;
&gt; &gt; &gt;
&gt; &gt; 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
&gt; &gt;
&gt; &gt; &gt;
&gt; &gt; &gt; (some of the words running together are not in the actual
&gt; &gt; change)
&gt; &gt; &gt;
&gt; &gt; &gt; I'm open to moving it elsewhere but developers will need to know
&gt; &gt; &gt; how to
&gt; &gt; &gt; at least find that or they will have trouble fixing build
&gt; &gt; issues.
&gt; &gt; &gt;
&gt; &gt; &gt; Regards,
&gt; &gt; &gt; Michael
&gt; &gt; &gt;
&gt; &gt; &gt;
&gt; &gt; &gt; On 4/19/2022 9:46 PM, Chao Li wrote:
&gt; &gt; &gt; &gt; Hi Micheal,
&gt; &gt; &gt; &gt; Using the way your provided the link, I found the detail log,
&gt; &gt; &gt; thanks,
&gt; &gt; &gt; &gt; but this way is not friendly to newbies, because they don't
&gt; &gt; &gt; know how to
&gt; &gt; &gt; &gt; find the tutorial.:)
&gt; &gt; &gt; &gt;
&gt; &gt; &gt; &gt; --
&gt; &gt; &gt; &gt; Thanks,
&gt; &gt; &gt; &gt; Chao
&gt; &gt; &gt; &gt; ------------------------
&gt; &gt; &gt; &gt;
&gt; &gt; &gt; &gt;
&gt; &gt; &gt; &gt; On 4月 20 2022, at 7:43 早上, "Michael Kubacki"
&gt; &gt; &gt; &gt; <mikuback@...> wrote:
&gt; &gt; &gt; &gt;
&gt; &gt; &gt; &gt; The wiki update is here:
&gt; &gt; &gt; &gt;
&gt; &gt; &gt;
&gt; &gt; 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
&gt; &gt;
&gt; &gt; &gt; &gt;
&gt; &gt; &gt; &gt; I am waiting for permissions to be updated so I can update
&gt; &gt; &gt; the actual
&gt; &gt; &gt; &gt; wiki page and then I'll send a patch for the plugin change
&gt; &gt; &gt; with the link
&gt; &gt; &gt; &gt; to that section.
&gt; &gt; &gt; &gt;
&gt; &gt; &gt; &gt; Regards,
&gt; &gt; &gt; &gt; Michael
&gt; &gt; &gt; &gt;
&gt; &gt; &gt; &gt; On 4/19/2022 6:15 PM, Michael Kubacki wrote:
&gt; &gt; &gt; &gt; &gt; I agree that is ideal but I'm not aware of how to do that
&gt; &gt; &gt; at the
&gt; &gt; &gt; &gt; moment.
&gt; &gt; &gt; &gt; &gt;
&gt; &gt; &gt; &gt; &gt; Thanks,
&gt; &gt; &gt; &gt; &gt; Michael
&gt; &gt; &gt; &gt; &gt;
&gt; &gt; &gt; &gt; &gt; On 4/19/2022 4:52 PM, Michael D Kinney wrote:
&gt; &gt; &gt; &gt; &gt;&gt; Hi Michael,
&gt; &gt; &gt; &gt; &gt;&gt;
&gt; &gt; &gt; &gt; &gt;&gt; Can the build log provide a direct link to the log file
&gt; &gt; &gt; artifact
&gt; &gt; &gt; &gt; if an
&gt; &gt; &gt; &gt; &gt;&gt; error is detected?
&gt; &gt; &gt; &gt; &gt;&gt;
&gt; &gt; &gt; &gt; &gt;&gt; Mike
&gt; &gt; &gt; &gt; &gt;&gt;

&gt; &gt; &gt; &gt; &gt;&gt;&gt; -----Original Message-----
&gt; &gt; &gt; &gt; &gt;&gt;&gt; From: devel@edk2.groups.io <devel@edk2.groups.io> On
&gt; &gt; &gt; Behalf Of
&gt; &gt; &gt; &gt; &gt;&gt;&gt; Michael Kubacki
&gt; &gt; &gt; &gt; &gt;&gt;&gt; Sent: Tuesday, April 19, 2022 12:42 PM
&gt; &gt; &gt; &gt; &gt;&gt;&gt; To: devel@edk2.groups.io; quic_rcran@...;
&gt; &gt; &gt; &gt; &gt;&gt;&gt; spbrogan@...; Chao Li <lichao@...>
&gt; &gt; &gt; &gt; &gt;&gt;&gt; Subject: Re: [edk2-devel] Some questions about Azure CI
&gt; &gt; &gt; &gt; &gt;&gt;&gt;
&gt; &gt; &gt; &gt; &gt;&gt;&gt; Hi Rebecca,
&gt; &gt; &gt; &gt; &gt;&gt;&gt;
&gt; &gt; &gt; &gt; &gt;&gt;&gt; We are trying to keep the results reporting experience
&gt; &gt; &gt; &gt; consistent with
&gt; &gt; &gt; &gt; &gt;&gt;&gt; other plugins and prevent an overwhelming amount of
&gt; &gt; &gt; information
&gt; &gt; &gt; &gt; being
&gt; &gt; &gt; &gt; &gt;&gt;&gt; printed to the build log.
&gt; &gt; &gt; &gt; &gt;&gt;&gt;
&gt; &gt; &gt; &gt; &gt;&gt;&gt; In case other errors are present, providing high-level
&gt; &gt; &gt; &gt; information from
&gt; &gt; &gt; &gt; &gt;&gt;&gt; each plugin can help point the user in the right
&gt; &gt; direction to
&gt; &gt; &gt; &gt; get more
&gt; &gt; &gt; &gt; &gt;&gt;&gt; detail.
&gt; &gt; &gt; &gt; &gt;&gt;&gt;
&gt; &gt; &gt; &gt; &gt;&gt;&gt; I completely understand the concern though, so I'm
&gt; &gt; &gt; planning to make
&gt; &gt; &gt; &gt; &gt;&gt;&gt; another step toward providing more information about
&gt; &gt; how to
&gt; &gt; &gt; &gt; debug an
&gt; &gt; &gt; &gt; &gt;&gt;&gt; issue, when it occurs. That is to put the step-by-step
&gt; &gt; &gt; &gt; information about
&gt; &gt; &gt; &gt; &gt;&gt;&gt; where to find the file diff into the EDK II Code
&gt; &gt; Formatting
&gt; &gt; &gt; &gt; wiki page
&gt; &gt; &gt; &gt; &gt;&gt;&gt; and then if a failure occurs, print a link to that
&gt; &gt; section of
&gt; &gt; &gt; &gt; the wiki
&gt; &gt; &gt; &gt; &gt;&gt;&gt; page. I am hoping this will provide sufficient
&gt; &gt; information to
&gt; &gt; &gt; &gt; get to the
&gt; &gt; &gt; &gt; &gt;&gt;&gt; file diff at the point of failure.
&gt; &gt; &gt; &gt; &gt;&gt;&gt;
&gt; &gt; &gt; &gt; &gt;&gt;&gt; I should be able to send these patches later today.
&gt; &gt; &gt; &gt; &gt;&gt;&gt;
&gt; &gt; &gt; &gt; &gt;&gt;&gt; Regards,
&gt; &gt; &gt; &gt; &gt;&gt;&gt; Michael
&gt; &gt; &gt; &gt; &gt;&gt;&gt;
&gt; &gt; &gt; &gt; &gt;&gt;&gt; On 4/19/2022 12:43 PM, Rebecca Cran wrote:
&gt; &gt; &gt; &gt; &gt;&gt;&gt;&gt; Since people are going to keep running into this,
&gt; &gt; could we
&gt; &gt; &gt; &gt; just output
&gt; &gt; &gt; &gt; &gt;&gt;&gt;&gt; the file diff to the console? That would avoid having
&gt; &gt; to go
&gt; &gt; &gt; &gt; hunting for
&gt; &gt; &gt; &gt; &gt;&gt;&gt;&gt; the log file.
&gt; &gt; &gt; &gt; &gt;&gt;&gt;&gt;
&gt; &gt; &gt; &gt; &gt;&gt;&gt;
&gt; &gt; &gt; &gt; &gt;&gt;&gt;
&gt; &gt; &gt; &gt; &gt;&gt;&gt;
&gt; &gt; &gt; &gt; &gt;&gt;&gt;
&gt; &gt; &gt; &gt; &gt;&gt;
&gt; &gt; &gt; &gt; &gt;&gt;
&gt; &gt; &gt; &gt; &gt;&gt;
&gt; &gt; &gt; &gt; &gt;&gt;
&gt; &gt; &gt; &gt; &gt;&gt;
&gt; &gt; &gt; &gt; &gt;&gt;
&gt; &gt; &gt; &gt;
&gt; &gt; &gt; &gt;
&gt; &gt; &gt; &gt; Sent from Mailspring
&gt; &gt; &gt;
&gt; &gt; &gt; Sent from Mailspring
&gt; &gt;
&gt; &gt; Sent from Mailspring
&gt; &gt;
&gt; &gt;
&gt; &gt;
&gt; &gt; /本邮件及其附件含有龙芯中科的商业秘密信息,仅限于发送给上面地址中列出的
&gt; &gt; 个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、
&gt; &gt; 复制或散发)本邮件及其附件中的信息。如果您错收本邮件,请您立即电话或邮件
&gt; &gt; 通知发件人并删除本邮件。
&gt; &gt; This email and its attachments contain confidential information from
&gt; &gt; Loongson Technology , which is intended only for the person or entity
&gt; &gt; whose address is listed above. Any use of the information contained
&gt; &gt; herein in any way (including, but not limited to, total or partial
&gt; &gt; disclosure, reproduction or dissemination) by persons other than the
&gt; &gt; intended recipient(s) is prohibited. If you receive this email in error,
&gt; &gt; please notify the sender by phone or email immediately and delete it. /
&gt; &gt;
</https:></mailto:devel+owner@edk2.groups.io></https:></https:></https:></https:></lichao@...></devel@edk2.groups.io></mikuback@...></mikuback@...></https:></https:></lichao@...></https:></https:></mikuback@...></spbrogan@...></quic_rcran@...></michael.d.kinney@...></devel@edk2.groups.io></mikuback@...></devel@edk2.groups.io></lichao@...></spbrogan@...></quic_rcran@...></michael.d.kinney@...></bob.c.feng@...></shenglei.zhang@...></mikuback@...>

本邮件及其附件含有龙芯中科的商业秘密信息,仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制或散发)本邮件及其附件中的信息。如果您错收本邮件,请您立即电话或邮件通知发件人并删除本邮件。
This email and its attachments contain confidential information from Loongson Technology , which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this email in error, please notify the sender by phone or email immediately and delete it.