Skip to content

Update trace #2929

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 2 commits into from
Oct 7, 2016
Merged

Update trace #2929

merged 2 commits into from
Oct 7, 2016

Conversation

SeppoTakalo
Copy link
Contributor

Description

Update mbed-trace library.

Fix in PelionIoT/mbed-trace#51 still had possibility of unexpected behavior as the mutex_lock_count variable might get modified after releasing mutex during last loop iteration. Should be fixed now on PelionIoT/mbed-trace#52

This PR merges in a latest master of mbed-trace branch. (Containing the fix).

Status

READY

Migrations

NO

Related PRs

PelionIoT/mbed-trace#52

Seppo Takalo added 2 commits October 5, 2016 16:09
…69..31e338c

31e338c Use temp variable in mutex release loop (#52)

git-subtree-dir: features/FEATURE_COMMON_PAL/mbed-trace
git-subtree-split: 31e338c23934491fcb852ee4d2788d34851d01a2
* commit '7a4b3d11a35f764d887b1a8c7a31b1944d2c9c46':
  Squashed 'features/FEATURE_COMMON_PAL/mbed-trace/' changes from b17e969..31e338c
@SeppoTakalo
Copy link
Contributor Author

CC: @yogpan01 @0xc0170 @sg-
Please merge this in. Thanks.

@c1728p9
Copy link
Contributor

c1728p9 commented Oct 5, 2016

/morph test

@bridadan
Copy link
Contributor

bridadan commented Oct 5, 2016

We had bot issues last night unfortunately. Running again.

/morph test

@mbed-bot
Copy link

mbed-bot commented Oct 5, 2016

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 1058

All builds and test passed!

@c1728p9
Copy link
Contributor

c1728p9 commented Oct 5, 2016

Looks good

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

Successfully merging this pull request may close these issues.

5 participants