DO NOT MERGE - Mbed TLS update RC1

[k-stachowiak]

Description

This PR imports a release candidate of the Mbed TLS library

Please DO NOT MERGE it. It has been raised in order for the CI to have a run at it.

[cmonr]

Welp, let's put it in the queue and hope for the best!

/morph build

[mbed-ci]

Build : FAILURE

Build number : 2968
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/7940/

[0xc0170]

Please review the build failures (most of them I checked fail with mbedtls_aes_crypt_ofb undefined)

[k-stachowiak]

I'm on it. @yanesca from the crypto team has proposed a solution that I am now testing locally. I will update the PR as soon as I get a basic test done on my machine.

[k-stachowiak]

I have pushed the change suggested by the crypto team. It built and ran on my local setup, but I don't have a way to test it against the failing targets, so let's see, how the failing boards do in the CI now.

[0xc0170]

/morph build

[mbed-ci]

Build : SUCCESS

Build number : 2972
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/7940/

Triggering tests

/morph test
/morph export-build
/morph mbed2-build

[mbed-ci]

Exporter Build : FAILURE

Build number : 2586
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/7940/

[0xc0170]

One of the failures "NUCLEO_F767ZI_make_iar/sources/examples/mbed-os-example-mesh-minimal/main.cpp",39 Fatal error[Pe1696]: cannot open source file "NanostackRfPhyAtmel.h"

most of them I checked are regarding this mesh minimal example. Not certain how is it related to the changes here? Please review

@SeppoTakalo is reviewing, will update

[k-stachowiak]

@sbutcher-arm @yanesca Could you please check if this may be induced by Mbed TLS changes? I'm already out of office, so I just briefly looked at the issue, and don't see a direct connection with our library.

[0xc0170]

@sbutcher-arm @yanesca Could you please check if this may be induced by Mbed TLS changes? I'm already out of office, so I just briefly looked at the issue, and don't see a direct connection with our library.

@SeppoTakalo Is this an example issue not related to this PR, so will be fixed separately and this rerun?

[SeppoTakalo]

I have broken the exported builds while preparing applications to #7814

So this will be fixed once that is in.

[0xc0170]

Note : only exporters are affect, testing in progress. We will restart exporters once connectivity is in.

[mbed-ci]

Test : FAILURE

Build number : 2725
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/7940/2725

[oliverjharper]

@0xc0170 I see ci-morph-test job has failed but test report appears OK, can you confirm?

[cmonr]

@oliverjharper We've been seeing these sync issues all over the place.

[cmonr]

/morph test

[mbed-ci]

Test : SUCCESS

Build number : 2734
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/7940/2734

[NirSonnenschein]

@0xc0170 @cmonr this seems to have passed the tests but there is an exporter failure.

[cmonr]

@SeppoTakalo #7940 (comment)

Does this mean CI needs to be rerun, or does the PR need to be updated first?

[SeppoTakalo]

@cmonr Re-running exporters should be enough, as I just touched the example applications, and by doing that I broke all others than #7814.

I don't see the need of full re-test.

[cmonr]

/morph export-build

[mbed-ci]

Exporter Build : SUCCESS

Build number : 2593
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/7940/