Release candidate for mbed-os-5.4.2 #4025
Conversation
…---+--------+ | test case | passed | failed | result | +---------------------------+--------+--------+--------+ | mbedtls_aes_self_test | 1 | 0 | OK | | mbedtls_entropy_self_test | 1 | 0 | OK | | mbedtls_sha256_self_test | 1 | 0 | OK | | mbedtls_sha512_self_test | 1 | 0 | OK | +---------------------------+--------+--------+--------+
…dtls_device.h remove function alternate defines (not used as we replace the full module)
…(unrequired removed + other moved to aes_alt.h) hcryp_aes moved to mbedtls_aes_context to allow multi instances remove ctx->nr, ctx->buf doxygen comments are removed (kept in .h file) function _ALT are removed (full module _ALT) handle error returned by HAL_CRYPxx functions aes is symetric, remove the dupplicated set_key_enc and set_key_dec buffer, and factorize the call to set_key function
Calling Thread::start multiple times leads to undefined behavior since the Thread class was not designed to handle being restarted. Return an error code if Thread::start is called a second time to prevent this behavior.
If a thread hasn't been started return Inactive as the status when Thread::get_state() is called.
Make the copy constructor and assignment operator private to prevent them from being used.
Resolves the github issue #3790: Blinky fails to build (on Mac) after addition of linker script preprocessing feature. Paraphrasing, this issue is that Homebrew on mac does not install `arm-none-eabi-gcc` in the same location as `arm-none-eabi-cpp`, the C Pre-Processor. The tools prior to this commit, and after turning on the pre-processing of the linker-script will fail on any Mac homebrew installed toolchains. This commit resolves the above issue by allowing the toolchain's path to the executable to remain empty after a call to `check_executable`. When this path is empty, the tools will search the PATH environment variable for the executable.
Currently, there is the issue in register setting into serial_format(). The issue is that parameter for baudrate setting is initialed zero in this function. In baudrate is less 9600bps, the issue occurs. In baudrate is over 9600, not occurs. When call serial_baud() before serial_format(), baudrate override and set with an incorrect value. Therefore, I fixed register setting not to set the parameter of baudrate setting in serial_format().
Add an 'all' parameter to get_flash_algorthim_binary. When set an enumerator of all flash algorithms is returned. rather than just the first flash algorithm.
Use python's LooseVersion to get the correct version.
Rebuild the json files used by arm-pack-manager now that a bug in version selection has been fixed.
Load aliases.json from mbed-os rather than from a temporary directory.
In targets.json, add lf_clock_rc_calib_timer_interval and lf_clock_rc_calib_mode_config setting which are essential when using BLE In mbed_overrides.c, create valuables instead of doing printf, those valuables are intended to be used for debugging in runtime.
Change NUC472 analogin_api.c accordingly
|
/morph test-nightly |
|
/morph mbed2-release |
|
/morph export-build |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 144 All exports and builds passed! |
Result: UNSTABLEYour command has finished executing! Here's what you wrote!
|
Result: SUCCESSYour command has finished executing! Here's what you wrote!
OutputAll builds and test passed! |
|
@0xc0170 @bridadan please check if the #3939 could be returned. Its a release blocker for us. FYI: @JanneKiiskila @yogpan01 |
Anna is away for 2 days. From what I understood on Friday, this PR introduced some conflicts that were not easy to resolve. If you can help you and apply this patch to the 3939 (releaase candidate), that would be helpful |
* commit 'c8a16cc274fbbb074909690a78a9d2aaf5411d5a': Squashed 'features/FEATURE_COMMON_PAL/mbed-trace/' changes from 31e338c23..af5f59cd2
|
/morph test-nightly |
|
/morph mbed2-release |
|
/morph export-build |
Result: FAILUREYour command has finished executing! Here's what you wrote!
OutputExample Prep failed! |
Result: FAILUREYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 145 Exporter Build failed! |
Result: UNSTABLEYour command has finished executing! Here's what you wrote!
|
|
For once the mbed 2 tests were the most stable 😛 Ok, apollogies for the failure everybody. It looks likes the 2 morph jobs basically tripped up over each other (they were both oddly using the same directories when they shouldn't have been). I will kick off replacement tests. Please do not start any more jobs, thanks. /morph test-nightly |
|
/morph export-build |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 146 All exports and builds passed! |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
OutputAll builds and test passed! |
|
Thanks @bridadan |
|
Should be noted that we actually have more regressions for the mbed 2 testing: We do periodically get some serial and timeout failures, but I am more concerned about the Interrupt vector relocation, semihost file system and RTOS failures which appear to be new...These should have been looked at and commented on before the release candidate was merged... |
|
Checking previous runs: SUMMARY |
|
Thanks for checking the results @adbridge. Maybe @geky and/or @simonqhughes can take a look at the semihost failure? |
|
We will ship with this as a known issue for v139 but yes it would be good for @geky or @simonqhughes to take a look at the failure to see it is reproducible or a one off. |
|
Currently looking into it. Related issue: #3983 |
|
There is a fix up #3773, however it's relatively involved and probably restricted to 5.5 |
No description provided.