public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Chao Li" <lichao@loongson.cn>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"mikuback@linux.microsoft.com" <mikuback@linux.microsoft.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"\"michael.d.kinney@intel.com\"" <michael.d.kinney@intel.com>,
	"\"quic_rcran@quicinc.com\"" <quic_rcran@quicinc.com>,
	"\"spbrogan@outlook.com\"" <spbrogan@outlook.com>
Subject: Re: [edk2-devel] Some questions about Azure CI
Date: Wed, 20 Apr 2022 18:10:15 +0800	[thread overview]
Message-ID: <CA5CE175-A392-4D5E-9BE9-392B7A97BB32@getmailspring.com> (raw)
In-Reply-To: <38e4e4f1-5fbd-bf3e-a274-6958f510dc4b@linux.microsoft.com>

[-- Attachment #1: Type: text/plain, Size: 5157 bytes --]

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/CA5CE175-A392-4D5E-9BE9-392B7A97BB32@getmailspring.com/0?redirect=https%3A%2F%2Fgithub.com%2Fmakubacki%2Ftianocore.github.io%2Fblob%2Fadd_ci_uncrustify_instructions%2FEDK-II-Code-Formatting.md%23how-to-find-uncrustify-formatting-errors-in-continuous-integration-ci&recipient=ZGV2ZWxAZWRrMi5ncm91cHMuaW8%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/CA5CE175-A392-4D5E-9BE9-392B7A97BB32@getmailspring.com/1?redirect=https%3A%2F%2Fdev.azure.com%2Fkilaterlee%2FLoongArch_edk2%2F_build%2Fresults%3FbuildId%3D31%26view%3Dlogs%26j%3D9701361e-2546-5093-77e5-58c75d95b7ce%26t%3D27131ef8-75e1-57c3-3236-d806181f2f1f&recipient=ZGV2ZWxAZWRrMi5ncm91cHMuaW8%3D).

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

On 4月 20 2022, at 9:56 上午, "Michael Kubacki" <mikuback@linux.microsoft.com> 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@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_rcran@quicinc.com;
> > >>> spbrogan@outlook.com; Chao Li <lichao@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
> > 
>


[-- Attachment #2: Type: text/html, Size: 8029 bytes --]

  reply	other threads:[~2022-04-20 10:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-19  4:42 Some questions about Azure CI Chao Li
2022-04-19 16:39 ` [edk2-devel] " Sean
2022-04-19 16:43   ` Rebecca Cran
2022-04-19 19:41     ` Michael Kubacki
2022-04-19 20:52       ` Michael D Kinney
2022-04-19 22:15         ` Michael Kubacki
2022-04-19 23:43           ` Michael Kubacki
2022-04-20  1:46             ` Chao Li
2022-04-20  1:56               ` Michael Kubacki
2022-04-20 10:10                 ` Chao Li [this message]
2022-04-20 11:08                   ` Chao Li
2022-04-20 14:45                     ` Michael Kubacki
2022-04-21  1:34                       ` Chao Li
     [not found]                       ` <16E7C575D2AAB8FB.27458@groups.io>
2022-05-16  5:15                         ` Chao Li
2022-05-16 16:12                           ` Michael Kubacki
2022-05-23  1:46                             ` Chao Li
2022-09-06 14:14                             ` 回复:Re: " Chao Li
2022-09-06 18:31                               ` Michael D Kinney
2022-04-20  1:59             ` Michael Kubacki
2022-04-19 23:39   ` 回复: " gaoliming
2022-04-21  8:52     ` 回复: edk2-devel] " Chao Li
2022-04-24  0:51       ` 回复: [edk2-devel] " gaoliming

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=CA5CE175-A392-4D5E-9BE9-392B7A97BB32@getmailspring.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