Skip to content

Fix traceback when running mbed test #8782

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 1 commit into from
Nov 19, 2018

Conversation

bridadan
Copy link
Contributor

Description

This should fix #8619.

The issue came down to the use of the Python function map() and that being present in a data structure that is serialized to json. Turns out, you can't serialize the output of map()! (Hence the error). This wraps the call to map in list() to force it to be serializable.

Pull request type

[x] Fix
[ ] Refactor
[ ] Target update
[ ] Functionality change
[ ] Docs update
[ ] Test update
[ ] Breaking change

@cmonr
Copy link
Contributor

cmonr commented Nov 17, 2018

/morph build

@mbed-ci
Copy link

mbed-ci commented Nov 17, 2018

Build : SUCCESS

Build number : 3655
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/8782/

Triggering tests

/morph test
/morph export-build
/morph mbed2-build

@mbed-ci
Copy link

mbed-ci commented Nov 17, 2018

@mbed-ci
Copy link

mbed-ci commented Nov 17, 2018

@0xc0170 0xc0170 merged commit 8dc54f1 into ARMmbed:master Nov 19, 2018
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.

Python 3.6.0 errors when using mbed-os-5.10.2 with mbed test
5 participants