unfortunately that is expected, it doesn't affect the result of a job, i.e. if failed, it would have failed regardless of that. I haven't asked for that to be investigated more as it doesn't affect the outcomes of the job but I agree is weird and should be
dealt with eventually.
From: Bohdan.Hunko--- via TF-M <tf-m@lists.trustedfirmware.org>
Date: Wednesday, 11 February 2026 at 10:37
To: tf-m@lists.trustedfirmware.org <tf-m@lists.trustedfirmware.org>
Subject: [TF-M] Weird behavior of static-checks job
Hi All,
I se that http://ci.trustedfirmware.org/job/tf-m-static-checks/3233/consoleFull has
FAILURE in the log, but the job passed:
Include order test: FAILURE (warning)
Additionally there are some other errors – a suspect that they may lead to this weird behavior:
22:23:00 + ./tf-m-ci-scripts/jenkins/verify.py --category static --value 1 --verify-name static-checks --user ****
22:23:01 Error posting to verify-status: 404
22:23:01 Not found: verify-status~verifications
22:23:01
22:23:01 Could not check if verify-status plugin is installed
Is this expected?
Best regards,
Bohdan Hunko
Cypress Semiconductor Ukraine LLC
Senior Engineer
CSS ICW SW INT BFS SFW
Mobile: +380995019714
Bohdan.Hunko@infineon.com