-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Mbedtls fixes for 5.15.2 #12723
Mbedtls fixes for 5.15.2 #12723
Conversation
Unittests fixed 2 mbedtls functions were updated to reflect the api
Same content as in #12479 |
@AnttiKauppila, thank you for your changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This has the same issues as the original PR on master. If there can be only 2 possible conditional code paths then we should be using
#if
#else
#endif
Rather than
#if
#elif
#endif
Github states I hope we get CI config fixed today to restart tests |
Hi @AnttiKauppila there is only one branch :) mbed-os-5.15 that is what PRs are raised against , not specific releases. |
Failures in CI, seem unrelated;
And we are failing the examples, seems to me BLE is deprecated but we still do try it?
|
There was a misconfig in CI :( A fix landed recently, will restart |
Test run: FAILEDSummary: 1 of 10 test jobs failed Failed test jobs:
|
@ARMmbed/mbed-os-maintainers Could you retrigger the tests? |
We were waiting for the fixes, will do now (but might still fail, need to wait for couple of jobs to complete to prove its all fine) |
CI restarted |
Test run: FAILEDSummary: 1 of 11 test jobs failed Failed test jobs:
|
Jenkins says; "Nice one! All 7645 tests for this pipeline are passing.". |
@JanneKiiskila Check the Pipeline K66F + ESP8266 combo fails |
Fatal error: ... mbed-os-greentea_K66F-ESP8266_ARM.tar.gz" does not exist |
I'll restarted the test (we already have CI passing in other jobs, the config should be correct now) |
Restarting entire pipeline (looks like devices are not as in later jobs) |
Test run: FAILEDSummary: 1 of 11 test jobs failed Failed test jobs:
|
@AnttiKauppila @ARMmbed/mbed-os-test Failed with dns failure for one target, how can we fix this one (not related to this PR). Is this network related issue, code (target/test) is fine on 5.15 branch? |
We got internal ticket for tracking this, ONME-4498 |
The latest restart overnight worked, ready to go in |
Summary of changes
This is a preparation PR for upcoming MbedTLS optimisation changes.
In the commits there are mostly flagged out code and this must not break anything.
Impact of changes
Migration actions required
Documentation
None, optimisations will be documented in MbedTLS optimisation release
Pull request type
Test results
Reviewers
@sbutcher-arm @jarvte @kivaisan