Hi Chris,

The CI job was trigged from https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/3521, you could find a list of all jobs and status of each job on Gerrit page that triggered by that job, job list example can be found at the end of this email. Another way is from the link you mentioned, that is a pipeline of how CI jobs start from one stage to another stage, if you click on the node of each stage, "Triggered Builds" will list the related job and you can check the details of it.

The Open CI for TF-M is under development of Linaro, development plan and status can be found from https://developer.trustedfirmware.org/w/collaboration/openci/ , it is not stable at this moment that we are continuously addressing on. There is no latest document for detail introduction of current Open CI yet. Open CI - developer.trustedfirmware.orghttps://developer.trustedfirmware.org/w/collaboration/openci/ Milestone Deliverables Target Completion Status; M1: Planning, Handover and Deployment SOW and project plan Hand over from OCE to Developer Services developer.trustedfirmware.org For the checkpatch job, it is a part of the static check stage, the error from this stage won't impact the final CI score, we need more investigation before active all static checks. The CI jobs were not able to trigger manually. There is a request to Linaro for the requirement that already working on, hope it can be deployed to the public Open CI soon.

Job list example on Gerrit after CI job:

Passed: 4, Failed: 18, Not done: 0 AN519_GNUARM_ConfigRegressionIPCTfmLevel2_Release_BL2http://ci.trustedfirmware.org/job/tf-m-build-config/29147/ -1 AN519_GNUARM_ConfigRegressionIPC_Release_BL2http://ci.trustedfirmware.org/job/tf-m-build-config/29146/ -1 AN519_GNUARM_ConfigRegressionProfileS_Release_BL2http://ci.trustedfirmware.org/job/tf-m-build-config/29152/ -1 AN519_GNUARM_ConfigRegression_Release_BL2http://ci.trustedfirmware.org/job/tf-m-build-config/29144/ -1 .... checkpatchhttp://ci.trustedfirmware.org/job/tf-m-checkpatch/472/ -1 cppcheckhttp://ci.trustedfirmware.org/job/tf-m-cppcheck/472/ 1 lava_boothttp://ci.trustedfirmware.org/job/tf-m-build-and-test/474/ 1 lava_testhttp://ci.trustedfirmware.org/job/tf-m-build-and-test/474/ 1 psoc64_GNUARM_ConfigRegressionIPCTfmLevel2_Release_NOBL2http://ci.trustedfirmware.org/job/tf-m-build-config/29157/ -1 psoc64_GNUARM_ConfigRegressionIPC_Release_NOBL2http://ci.trustedfirmware.org/job/tf-m-build-config/29154/ -1 tf-m-buildhttp://ci.trustedfirmware.org/job/tf-m-build-and-test/479/ -1 tf-m-build-docshttp://ci.trustedfirmware.org/job/tf-m-build-docs/647/ 1

Thanks, Karl Zhang ________________________________ From: TF-M tf-m-bounces@lists.trustedfirmware.org on behalf of Christopher Brand via TF-M tf-m@lists.trustedfirmware.org Sent: Tuesday, September 1, 2020 12:35 AM To: tf-m@lists.trustedfirmware.org tf-m@lists.trustedfirmware.org Subject: [TF-M] CI Checkpatch

So I see the CI system runs checkpatch, but I don’t see any mention of checkpatch under the “docs” directory, or in any of the gerrit reviews, or even on the mailing list. The output in the CI system, as far as I can see, is not particularly useful (I followed the link posted on my review to https://ci.trustedfirmware.org/blue/organizations/jenkins/tf-m-static/detail... but could find anything indicating what issue was actually found).

Is there any documentation on how we can run checkptach manually? Or on how to see what the CI version is actually complaining about? Should I just be ignoring the CI checkpatch errors?

Thanks,

Chris Brand

Sr Prin Software Engr, MCD: WIRELESS

Cypress Semiconductor Corp.

An Infineon Technologies Company

#320-13700 International Place, Richmond, British Columbia V6V 2X8 Canada

www.infineon.comhttp://www.infineon.com www.cypress.comhttp://www.cypress.com

This message and any attachments may contain confidential information from Cypress or its subsidiaries. If it has been received in error, please advise the sender and immediately delete this message.