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.1906.1650411785739614413 for ; Tue, 19 Apr 2022 16:43:05 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@linux.microsoft.com header.s=default header.b=Q8hn9Vq5; 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 5EF5620E1AAD; Tue, 19 Apr 2022 16:43:04 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com 5EF5620E1AAD DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com; s=default; t=1650411785; bh=2yudiwd6hrrmcwHYKxvTMwNGg6NNll/vCSmMkiE1wcY=; h=Date:Subject:From:To:References:In-Reply-To:From; b=Q8hn9Vq5pW8FK4Ye/oAJvHdkcPgT5a+wfecPyXqbvlX6f/SX7YJaJc4qZ8zH824Qu RLxzkgUhFxuKKgcPD0mMWnoHcAPawuEeAiJyHNQRaGCSzEAzscOWV6nD4eOnidqTlx HzVDZLvAVXSgZteSpJj+cPYq5fi/T7UppBEj45lI= Message-ID: <6c844825-2683-1a07-10ed-af4d4d275a92@linux.microsoft.com> Date: Tue, 19 Apr 2022 19:43:03 -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 From: "Michael Kubacki" To: devel@edk2.groups.io, michael.d.kinney@intel.com, "quic_rcran@quicinc.com" , "spbrogan@outlook.com" , Chao Li References: <21703.1650386347482946545@groups.io> <229fb259-4591-a03b-6fa0-71deec1d0405@quicinc.com> <9c66487e-959b-ed89-7705-cd9bbddee573@linux.microsoft.com> <4a6b8f38-625b-5dc4-aab6-863444030022@linux.microsoft.com> In-Reply-To: <4a6b8f38-625b-5dc4-aab6-863444030022@linux.microsoft.com> Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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 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 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. >>>> >>> >>> >>> >>> >> >> >> >> >> >>