Bret: ECC mainly checks the firmware source coding style. Host based unit test code may follow the different rule. I suggest to ignore ECC check result for them. The ignored file or directory can be added into the Package level ci.yaml file.
Thanks Liming 发件人: bounce+27952+65601+4905953+8761...@groups.io <bounce+27952+65601+4905953+8761...@groups.io> 代表 Bret Barkelew via groups.io 发送时间: 2020年9月25日 10:39 收件人: devel@edk2.groups.io 主题: [edk2-devel] ECC: main function entry point in host-based unit tests ERROR - EFI coding style error ERROR - *Error code: 7001 ERROR - *There should be no use of int, unsigned, char, void, long in any .c, .h or .asl files ERROR - *file: //home/corthon/_uefi/edk2_qemu_ci/edk2/MdeModulePkg/Library/VariablePolicyLi b/VariablePolicyUnitTest/VariablePolicyUnitTest.c ERROR - *Line number: 763 ERROR - *[main] Return type int ERROR - ERROR - EFI coding style error ERROR - *Error code: 8006 ERROR - *Function name does not follow the rules: 1. First character should be upper case 2. Must contain lower case characters 3. No white space characters ERROR - *file: //home/corthon/_uefi/edk2_qemu_ci/edk2/MdeModulePkg/Library/VariablePolicyLi b/VariablePolicyUnitTest/VariablePolicyUnitTest.c ERROR - *Line number: 2253 ERROR - *The function name [main] does not follow the rules Currently, the host-based unit tests are using a standard C entry point: int main () That’s going to break both of these. Another thing to override/figure out for host-based tests - Bret -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#65609): https://edk2.groups.io/g/devel/message/65609 Mute This Topic: https://groups.io/mt/77074863/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
