Skip to content

Release candidate for mbed-os-5.5.2 #4689

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 116 commits into from
Jul 4, 2017
Merged

Release candidate for mbed-os-5.5.2 #4689

merged 116 commits into from
Jul 4, 2017

Conversation

adbridge
Copy link
Contributor

@adbridge adbridge commented Jul 3, 2017

No description provided.

sarahmarshy and others added 30 commits July 3, 2017 11:46
"Browse information," or the indexer for MDK, causes extremely long
build times when enabled.
This commit implements a SPI mode which will offer better performance
thanks to usage of Lower Layer API which use fewer registers access,
at the cost of lower robustness (no error management).
- leds definition
- add sw4stm32 exporter
- recomment mco debug
Provide a more precise link to the docs.mbed.com page
If the file extra_targets.json exists in the working directory load it over the top of the built in targets.json for defining new and overriding built in mbed target definitions.
Recursively merge any target configs in extra_targets.json rather than completely replacing keys at the top level
Avoid duplication of update_target_data() code
Keep "custom_targets.json" filename definition in Targets()
@adbridge
Copy link
Contributor Author

adbridge commented Jul 3, 2017

/morph test-nightly

@adbridge
Copy link
Contributor Author

adbridge commented Jul 3, 2017

/morph mbed2-release

@adbridge
Copy link
Contributor Author

adbridge commented Jul 3, 2017

/morph export-build

@mbed-bot
Copy link

mbed-bot commented Jul 3, 2017

Result: FAILURE

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

/morph mbed2-release

Output

mbed Build Number: 33

Build failed!

@mbed-bot
Copy link

mbed-bot commented Jul 3, 2017

Result: FAILURE

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

/morph export-build

Output

mbed Build Number: 77

Exporter Build failed!

@adbridge
Copy link
Contributor Author

adbridge commented Jul 3, 2017

/morph mbed2-release

@mbed-bot
Copy link

mbed-bot commented Jul 3, 2017

Result: SUCCESS

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

/morph mbed2-release

@mbed-bot
Copy link

mbed-bot commented Jul 3, 2017

Result: ABORTED

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

/morph test-nightly

Output

mbed Build Number: 722

Test failed!

@studavekar
Copy link
Contributor

/morph test-nightly

@mbed-bot
Copy link

mbed-bot commented Jul 4, 2017

Result: SUCCESS

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

/morph test-nightly

Output

mbed Build Number: 725

All builds and test passed!

@studavekar
Copy link
Contributor

/morph export-build

@mbed-bot
Copy link

mbed-bot commented Jul 4, 2017

Result: FAILURE

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

/morph export-build

Output

mbed Build Number: 79

Exporter Build failed!

This definition requires IAR 7.80.2 and higher.
It will be readded once we all update to the latest IAR 7.80 patch release. For
future, please any new target should state what are the requirements on tools to
avoid this suprises.
@adbridge
Copy link
Contributor Author

adbridge commented Jul 4, 2017

/morph export-build

@adbridge
Copy link
Contributor Author

adbridge commented Jul 4, 2017

/morph test-nightly

@adbridge
Copy link
Contributor Author

adbridge commented Jul 4, 2017

/morph mbed2-release

@mbed-bot
Copy link

mbed-bot commented Jul 4, 2017

Result: SUCCESS

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

/morph export-build

Output

mbed Build Number: 81

All exports and builds passed!

@mbed-bot
Copy link

mbed-bot commented Jul 4, 2017

Result: SUCCESS

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

/morph mbed2-release

@adbridge
Copy link
Contributor Author

adbridge commented Jul 4, 2017

Weird nightly failure :

09:24:38 [1499178285.34][HTST][INF] {{result;success}}
09:24:38 mbedgt: checking for GCOV data...
09:24:38 mbedgt: mbed-host-test-runner: stopped and returned 'OK'
09:24:38 mbedgt: test on hardware with target id: 500200001d17283f00000000000000000000000097969902
09:24:38 mbedgt: test suite 'tests-mbed_drivers-ticker' ....................................................... OK in 55.52 sec
09:24:38 	test case: 'Timers: 1x ticker' ............................................................... OK in 11.05 sec
09:24:38 	test case: 'Timers: 2x tickers' .............................................................. ERROR in 0.00 sec

@studavekar Looks like the test case passed but the result didn't get propagated to the host?
Restarting...

@mbed-bot
Copy link

mbed-bot commented Jul 4, 2017

Result: ABORTED

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

/morph test-nightly

Output

mbed Build Number: 727

Test failed!

@adbridge
Copy link
Contributor Author

adbridge commented Jul 4, 2017

/morph test-nightly

@mbed-bot
Copy link

mbed-bot commented Jul 4, 2017

Result: SUCCESS

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

/morph test-nightly

Output

mbed Build Number: 728

All builds and test passed!

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.