From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from loongson.cn (loongson.cn [114.242.206.163]) by mx.groups.io with SMTP id smtpd.web10.683.1650343331446047063 for ; Mon, 18 Apr 2022 21:42:12 -0700 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: loongson.cn, ip: 114.242.206.163, mailfrom: lichao@loongson.cn) Received: from lichao-PC (unknown [10.40.24.65]) by mail.loongson.cn (Coremail) with SMTP id AQAAf9AxWs2ePV5ipJEoAA--.10473S2; Tue, 19 Apr 2022 12:42:06 +0800 (CST) Date: Tue, 19 Apr 2022 12:42:06 +0800 From: "Chao Li" To: "=?utf-8?Q?devel=40edk2.groups.io?=" , "=?utf-8?Q?Bret.Barkelew=40microsoft.com?=" , "=?utf-8?Q?sean.brogan=40microsoft.com?=" Cc: "=?utf-8?Q?michael.d.kinney=40intel.com?=" , "=?utf-8?Q?gaoliming=40byosoft.com.cn?=" Message-ID: Subject: Some questions about Azure CI X-Mailer: Mailspring MIME-Version: 1.0 X-CM-TRANSID: AQAAf9AxWs2ePV5ipJEoAA--.10473S2 X-Coremail-Antispam: 1UD129KBjvJXoW7ZFy7ur13uFyrtFW7tFWfAFb_yoW8Gr4Upa 9akr1avrZ8Gr48Jas0kw1FgFnIgr97WayUX3Wjgw1xGa1Uuwnrtw40krWF9a43AryvvrW8 Zwn093WDWFn0qFJanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUPab7Iv0xC_Kw4lb4IE77IF4wAFF20E14v26r1j6r4UM7CY07I2 0VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rw A2F7IY1VAKz4vEj48ve4kI8wA2z4x0Y4vE2Ix0cI8IcVAFwI0_Jr0_JF4l84ACjcxK6xII jxv20xvEc7CjxVAFwI0_Jr0_Gr1l84ACjcxK6I8E87Iv67AKxVW8Jr0_Cr1UM28EF7xvwV C2z280aVCY1x0267AKxVW0oVCq3wAS0I0E0xvYzxvE52x082IY62kv0487Mc02F40Eb7x2 x7xS6r1j6r4UMc02F40EFcxC0VAKzVAqx4xG6I80ewAqx4xG64kEw2xG04xIwI0_Gr0_Xr 1l5I8CrVC2j2CEjI02ccxYII8I67AEr4CY67k08wAv7VC0I7IYx2IY67AKxVWUJVWUGwAv 7VC2z280aVAFwI0_Jr0_Gr1lOx8S6xCaFVCjc4AY6r1j6r4UM4x0Y48IcxkI7VAKI48JMx kIecxEwVCm-wCF04k20xvY0x0EwIxGrwCFx2IqxVCFs4IE7xkEbVWUJVW8JwC20s026c02 F40E14v26r106r1rMI8I3I0E7480Y4vE14v26r106r1rMI8E67AF67kF1VAFwI0_JF0_Jw 1lIxkGc2Ij64vIr41lIxAIcVC0I7IYx2IY67AKxVWUJVWUCwCI42IY6xIIjxv20xvEc7Cj xVAFwI0_Jr0_Gr1lIxAIcVCF04k26cxKx2IYs7xG6rW3Jr0E3s1lIxAIcVC2z280aVAFwI 0_Jr0_Gr1lIxAIcVC2z280aVCY1x0267AKxVWUJVW8JbIYCTnIWIevJa73UjIFyTuYvjxU gAsgDUUUU X-CM-SenderInfo: xolfxt3r6o00pqjv00gofq/1tbiAQABCF3QvPNNKAACst Content-Type: multipart/alternative; boundary="625e3d9e_595ae839_7f9a" --625e3d9e_595ae839_7f9a Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi Sean and Bret, I prepare submit a new architecture code to edk2, and I have applied for an Azure ID. There have two questions when trigger the Azure CI, please refer to the following two links: 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 and https://dev.azure.com/kilaterlee/LoongArch_edk2/_build/results?buildId=31&view=logs&j=5e3952f2-9c8a-5394-82c1-a803bcab3ca3&t=444fd513-1d27-501b-b92c-56decf629da5. Question1: The CI tells me a fail that: "Test Failed: Uncrustify Coding Standard Test NO-TARGET", I'm not sure what happens when this class failure occurs, can you tell me what happened and how to fix it? Question2: There are many coding style errors with ECC(like: "Variable name does not follow the rules: 1. First character should be upper case 2. Must contain lower case characters 3. No white space characters 4. Global variable name must start with a 'g', *Member variable [BASE_LIBRARY_JUMP_BUFFER.S2] NOT follow naming convention."), but I found that other architectures have the same coding style as ours, can you tell me how to fix thus coding style error? Hope you reply, thank you very much. -- Thanks, Chao ------------------------ --625e3d9e_595ae839_7f9a Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Hi Sean and Bret,


Question1:
The CI tells me a fail that: =22Test =46ailed: Uncrustif= y Coding Standard Test NO-TARGET=22, I'm not sure wh= at happens when this class failure occurs, can you tell me what happened = and how to fix it=3F

Question2:
There are many coding style errors with ECC(like: =22Variable name doe= s not follow the rules: 1. =46irst character should be upper case 2. Must= contain lower case characters 3. No white space characters 4. Global var= iable name must start with a 'g', *Member variable =5BBASE=5FLIBRARY=5FJU= MP=5FBU=46=46ER.S2=5D NOT follow naming convention.=22), but I found that other architectures have the same coding style as o= urs, can you tell me how to fix thus coding style error=3F

= Hope you reply, thank you very much.


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


=
--625e3d9e_595ae839_7f9a--