Release candidate for mbed-os-5.2-rc3 #3033
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Locate *lwip_* in XRAM to fix IRAM OOM
Let's swap default PA_4 pin mapping to SPI_3 otherwise SPI3 cannot be used
Fix indentation issues, remove useless comments, correct if/else format
STM32F303ZE was introduced in parallel to the changes which consist in having family wide definitions like device.h file and a common objects definition. This target is updated accordingly now to benefit of SPI definitions.
Don't ask multiple DNS servers in case of successful connection, even if the response is negative. Make sure the return value is correct.
Use newlib nano for targets which have the key "default_lib" set to "small". Also support the legacy key of "default_build".
DEVICE_ are passed as command line -D, thus no inclusion is required. ``platform.h`` is C++ header file, should not be pulled in C files
Currently only one network interface can be compiled in at a given time, to avoid failing automated test on this target WiFi will be disabled by default.
Squash all the changes in the PR 2865 - "TARGET_NRF5: A few corrections in HAL implementation." This PR causes problems with the release script so a squashed version without merges is needed.
Manually bring PR 2865 into the release
|
/morph test-nightly |
Result: FAILUREYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 0 Test failed! |
|
Looking at the failures:
b) features-storage-feature_storage-tests-cfstore-find (FIND_test_05_end)
These tests did pass however on K64F/IAR
b) tests-mbed_drivers-lp_timeout
|
|
/morph test-nightly |
|
Hi @adbridge, these are known and expected to fail:
The failure on tests-events-queue was timing based, and was not a crash. It might be an intermittent failure. Either way I wouldn't block the release for it. In my opinion this is ready for RC3. @sg-, @bridadan, @0xc0170 what are your thoughts? |
Result: FAILUREYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 0 Test failed! |
|
As the test failures are expected I'm going to go ahead and merge this. |
This was referenced Oct 17, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.