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
Release candidate for mbed-os-5.8.6 #7109
Conversation
/morph build |
pr-head failing with:
|
If user adds USE_USER_DEFINED_HAL_ETH_MSPINIT macro in the json config, he can implement his own HAL_ETH_MspDeInit and HAL_ETH_MspDeInit functions.
Fixing a bug. .mbed is ignored in the high level .gitignore file. But .mbed is actually a needed file inside of tools/export. Even though the file is still in the main repo, since it's ignored now, you can easily lose it or remove it without seeing the change. Adding this .gitignore file here will add .mbed back into the tracked files for only this directory
genpinmap script version 1.1
Referencing to "UG257: EFM32 Pearl Gecko PG12 Starter Kit User's Guide - Chapter 4" (https://www.silabs.com/documents/public/user-guides/ug257-stk3402-usersguide.pdf) it should be like in this commit.
* Updated pinout of EXP header from pre-production to production * Move assignment of PF7 to SPI_2 to be compatible with the new SPI flash routing
* Since mbed does not overwrite itself, make the flashing routines run out of flash by default * Report a writeable size of 4 bytes (previously erroneously reported a full eraseable page as the minimum write size)
* IRQ handling got updated previously to a non-functional state when both callbacks were registered (it'd fire a fall callback for both rise and fall events). With this update, that faulty behaviour is corrected. Due to delays between the detection of the edge and the handling of the interrupt (and the fact that information about which edge you received on the pin is not stored anywhere), there is no way to be absolutely sure which edge got triggered on the pin. Therefore, we make a best-guess effort by looking at the pin state at the time of IRQ handling, and fire a callback as if that was the end state of the event. This will usually work out fine, except in cases were the signal is toggling faster than the IRQ handler's response time. In that case, a user won't get both callbacks (as expected for a pulse), but only the last event. * Stripped some dead code.
I fixed redeclaration of type name "bool_t" for target Renesas because this typedef has been defined in rtx_core_ca.h by #6273.
…osed to using Serial
Fixes one error: IOTCLT-2638 Hardfault during reconnection retry with Thread
…e resource that are not needed in cellular state machine.
60a0065
to
d87c289
Compare
Updated: Pushed loraradio tests to 5.9.1 |
/morph build |
pr-head failed this time because of:
|
Build : FAILUREBuild number : 2234 |
Build : FAILUREBuild number : 2235 |
The most recent failure appears to be caused by an update to the nanostack-border-router example for 5.9.0-rc1 testing, but which has broken 5.8 compatibility. |
/morph build |
Build : SUCCESSBuild number : 2241 Triggering tests/morph test |
@kjbracey-arm @OPpuolitaival Any ideas why cloud client example is failing with general SCM issues ?
|
No. I've just seen this on other PRs too: https://jenkins-internal.mbed.com/blue/organizations/jenkins/ARMmbed%2Fmbed-os-cliapp/detail/master/12226/pipeline/130 |
Weird it isn't even a consistent set of boards that are failing |
Seems jenkins problem. Asking support from infra team |
@OPpuolitaival Thanks, can we stress the urgency of this as it is blocking 5.8.6 candidate and could also impact any other PRs going into the 5.9 release... |
Exporter Build : SUCCESSBuild number : 1865 |
@miklis said that it is most probably limitation of github API calls |
@miklis @OPpuolitaival So how do we fix this, this was restarted twice and still failed ? |
Test : FAILUREBuild number : 2030 |
/morph test |
@OPpuolitaival Can we force the successful run status to this PR? I didn't realise you had kicked it off again so I restarted and then aborted and of course now the status is only showing aborted :( |
@adbridge I think that we need to run that again to get that check in green |
OK have restarted pr-head |
Test : SUCCESSBuild number : 2031 |
No description provided.