From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from linux.microsoft.com (linux.microsoft.com [13.77.154.182]) by mx.groups.io with SMTP id smtpd.web08.3127.1650419771112771110 for ; Tue, 19 Apr 2022 18:56:11 -0700 Authentication-Results: mx.groups.io; dkim=fail reason="body hash did not verify" header.i=@linux.microsoft.com header.s=default header.b=JEGv/2SC; spf=pass (domain: linux.microsoft.com, ip: 13.77.154.182, mailfrom: mikuback@linux.microsoft.com) Received: from [192.168.4.22] (unknown [47.201.46.36]) by linux.microsoft.com (Postfix) with ESMTPSA id C98AB20E2C07; Tue, 19 Apr 2022 18:56:09 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com C98AB20E2C07 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com; s=default; t=1650419770; bh=xo9/AzVl6CKupalD27jc49PBSY9zCEXxbtCDNlv0Lc4=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=JEGv/2SCc5tWKzCiWLLM9CZjHupeIrDulJHnr3xpbgGvU7NlkiaQFzgMvVJSGXGhc zXm76uW6QS40dRdbENQmRF9VNC5TH1x8RUnM5b/mi0OfJjWU0KMypXKDj+pkGtJ7P4 o96wEQQyOsTLHN/zopQ5FUFRDPZAGqdZ3Pwudyw0= Message-ID: <38e4e4f1-5fbd-bf3e-a274-6958f510dc4b@linux.microsoft.com> Date: Tue, 19 Apr 2022 21:56:08 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0 Subject: Re: [edk2-devel] Some questions about Azure CI To: devel@edk2.groups.io, lichao@loongson.cn Cc: "michael.d.kinney@intel.com" , "quic_rcran@quicinc.com" , "spbrogan@outlook.com" References: <6c844825-2683-1a07-10ed-af4d4d275a92@linux.microsoft.com> <158DA375-9351-413B-B748-2185873071E6@getmailspring.com> From: "Michael Kubacki" In-Reply-To: <158DA375-9351-413B-B748-2185873071E6@getmailspring.com> Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Hi Chao, Are you referring to the change I made to put the link to the=20 instructions in the build log. Here's an example of what that will look=20 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=3Dtrue (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=20 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,=20 > but this way is not friendly to newbies, because they don't know how to= =20 > find the tutorial.:) >=20 > -- > Thanks, > Chao > ------------------------ >=20 >=20 > On 4=E6=9C=88 20 2022, at 7:43 =E6=97=A9=E4=B8=8A, "Michael Kubacki"=20 > wrote: >=20 > The wiki update is here: > https://github.com/makubacki/tianocore.github.io/blob/add_ci_uncrusti= fy_instructions/EDK-II-Code-Formatting.md#how-to-find-uncrustify-formatting= -errors-in-continuous-integration-ci >=20 > 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 l= ink > to that section. >=20 > Regards, > Michael >=20 > 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 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 > >>> 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 m= ake > >>> 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. > >>>> > >>> > >>> > >>> > >>> > >> > >> > >> > >> > >> > >> >=20 >=20 > Sent from Mailspring >=20