toggle quoted messageShow quoted text
Can the build log provide a direct link to the log file artifact if an error is detected?
From: email@example.com <firstname.lastname@example.org> On Behalf Of Michael Kubacki
Sent: Tuesday, April 19, 2022 12:42 PM
To: email@example.com; quic_rcran@...; spbrogan@...; Chao Li <lichao@...>
Subject: Re: [edk2-devel] Some questions about Azure CI
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
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.
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.