From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"mikuback@linux.microsoft.com" <mikuback@linux.microsoft.com>,
"quic_rcran@quicinc.com" <quic_rcran@quicinc.com>,
"spbrogan@outlook.com" <spbrogan@outlook.com>,
Chao Li <lichao@loongson.cn>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] Some questions about Azure CI
Date: Tue, 19 Apr 2022 20:52:06 +0000 [thread overview]
Message-ID: <SA2PR11MB4938CCDFEB3DD1BBAA2F175AD2F29@SA2PR11MB4938.namprd11.prod.outlook.com> (raw)
In-Reply-To: <9c66487e-959b-ed89-7705-cd9bbddee573@linux.microsoft.com>
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.
> >
>
>
>
>
next prev parent reply other threads:[~2022-04-19 20:52 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 [this message]
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
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=SA2PR11MB4938CCDFEB3DD1BBAA2F175AD2F29@SA2PR11MB4938.namprd11.prod.outlook.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox