-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reject duplicated build steps in the outcome file #9286
base: development
Are you sure you want to change the base?
Reject duplicated build steps in the outcome file #9286
Conversation
Note "Reject duplicated build steps in the outcome file" seems very different from "use .s for assembly files" - presumably the latter could be a separate PR, making everything easier to review? |
@tom-cosgrove-arm You're right, this turned into “fix issues in all.sh”, mostly so that I could have distinct configuration names. I'll break that unexpected part out. |
I've split out the |
1073dd7
to
5c04140
Compare
5c04140
to
13d5b99
Compare
We no longer have two (only partially distinct) implementations of ECJ-PAKE cipher suites in TLS, now that the non-MBEDTLS_USE_PSA_CRYPTO implementation is being removed. We may want to add this testing back in the future, but we'll have to use an old Mbed TLS instead of a differently-built one. Mbed-TLS#9740 Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
13d5b99
to
ce25947
Compare
Add an outcome line when all.sh calls make. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
… builds Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
Some versions on CMake (on some platforms?) run make (not $(MAKE)) under the hood on targets named cmTC_* (CMake TryCompile). Ignore those calls. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
This should make failures.csv on the CI be a complete list of failures (although it will still have incomplete information on what has failed, if what failed wasn't tracked individually). Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
component_test_tfm_config_no_p256m was not building sample programs, but component_test_tfm_config_p256m_driver_accel_ec was. This is now flagged as a discrepancy by outcome analysis. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
This comes up in `psa_collect_statuses.py` and possibly (I didn't finish the analysis) some CMake builds, which were reporting duplicate `make` steps. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
As a debugging help, log the `make` command line in the outcome file. This is not accurate if a command line argument contains some special characters, but good enough to help debugging. Hopefully this will only be temporary. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
ce25947
to
b3940ab
Compare
When emitting a line for the outcome file for `make`, indicate if the target is being built in a different directory or with a different makefile. We don't currently do this explicitly with an ambiguous target name, but it happens under the hood with older versions of CMake (observed with CMake 3.10.2, not with CMake 3.22.1). Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
Resolves #9023
Status: work in progress, I want CI feedback
PR checklist
Please tick as appropriate and edit the reasons (e.g.: "backport: not needed because this is a new feature")