Skip to content

Release candidate for mbed-os-5.11.5-alpha #9719

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

Merged
merged 3 commits into from
Feb 14, 2019
Merged

Conversation

adbridge
Copy link
Contributor

@adbridge adbridge commented Feb 14, 2019

Description

This is a pre-release version of mbed-os-5.11.5 and includes commits from just 2 PRs that are urgently required by Cypress and the client guys.

Yossi Levy and others added 3 commits February 14, 2019 12:23
… derivation when there is no TRNG but there is DRBG
The WICED precompiled libraries submitted with mbed-os-5.11.4
were compiled against mbed-os master branch at #57d8915a:
https://github.com/ARMmbed/mbed-os/tree/57d8915a

At that moment, the master branch contained commits targeting
mbed-os-5.12, this prevented the libraries from functioning correctly
when manually picked to mbed-os-5.11 release branch.

The libraries are now compiled against #ecb3c8c:
https://github.com/ARMmbed/mbed-os/tree/ecb3c8c
Updated to 5.11.5 although this is actually an alpha release of that.
@adbridge adbridge requested a review from a team February 14, 2019 12:35
@0xc0170
Copy link
Contributor

0xc0170 commented Feb 14, 2019

Ci started

@@ -44,7 +44,7 @@
*
* @note 99 is default value for development version (master branch)
*/
#define MBED_PATCH_VERSION 4
#define MBED_PATCH_VERSION 5
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suppose...

@adbridge adbridge closed this Feb 14, 2019
@adbridge adbridge reopened this Feb 14, 2019
@adbridge
Copy link
Contributor Author

adbridge commented Feb 14, 2019

Argghhh somehow contrived to accidently click close on this ! No idea how :( now going to have to await ci again! Actually ci hadn't finished running so it may still report correctly if we're lucky.

@mbed-ci
Copy link

mbed-ci commented Feb 14, 2019

Test run: FAILED

Summary: 1 of 12 test jobs failed
Build number : 1
Build artifacts

Failed test jobs:

  • jenkins-ci/mbed-os-ci_greentea-test

@adbridge
Copy link
Contributor Author

First run got stuck and Aleksi aborted and restarted

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants