Nanostack update #4345
Nanostack update #4345
Conversation
… content from commit 1fc996d9f git-subtree-dir: features/FEATURE_COMMON_PAL/sal-stack-nanostack-eventloop git-subtree-split: 1fc996d9f5190b644b28589fb93b86479725b47f
…FEATURE_COMMON_PAL/sal-stack-nanostack-eventloop'
|
/morph test-nightly |
Result: ABORTEDYour command has finished executing! Here's what you wrote!
OutputTest failed! |
|
There was an intermittent issue with K22F board which failed to flash, have swapped the boards will keep an eye on the results. |
|
/morph test-nightly |
Result: ABORTEDYour command has finished executing! Here's what you wrote!
OutputBuild failed! |
|
The fix #4353 is merged in master /morph test-nightly |
Result: FAILUREYour command has finished executing! Here's what you wrote!
OutputTest failed! |
|
Looks like following tests failed:
Those tests are not using Nanostack and for me, it looks like they were able to build but within a test run, got some kind of failure. |
|
/morph test-nightly |
Result: FAILUREYour command has finished executing! Here's what you wrote!
OutputTest failed! |
|
@studavekar Lots of K64F timeout failures. Is this another board failure ? |
|
/morph test-nightly |
Result: FAILUREYour command has finished executing! Here's what you wrote!
OutputTest failed! |
|
NUCLEO_F429ZI failed lwip-tests-mbedmicro-net-udp_dtls_handshake with a lot of errors. Network errors perhaps? Will restart |
|
/morph test-nightly |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
OutputAll builds and test passed! |
|
@sg- Did you want to review this ? |
Description
Status
READY
Migrations
No changes to public API.
Test results
Tests done using mbed-os-example-mesh-minimal
Build & HW tests
(Sorry, internal links, not accessible from outside our network.)