-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[OOB 5.10] IP connectivity test failed #8028
Comments
@ARMmbed/mbed-os-test |
TCPSERVER_ACCEPT test case requires 2 devices. https://github.com/ARMmbed/mbed-os/blob/master/TEST_APPS/testcases/netsocket/TCPSERVER_ACCEPT.py#L38 The test result is inconclusive if only one device is found. |
@jonikula can you check this? I think that it could be nice to tell for example (1/2 suitable devices found) or some another way to make clear that need more devices |
That's something we could easily add to the logging and perhaps to the failure reason as well. |
@0xc0170 this is not a bug. Works as expected. I will create usability improvement ticket related to this. |
@OPpuolitaival can you please add a link to the enhancement as result of this effort? |
Hi guys, I've hit the same problem. I didn't understand why the test was inconclusive and whether I needed extra HW platforms. Here is a PR (#8073) with a good start, but IMO should be extended to explain those cases in more detail. Thanks! |
Description
Mbed OS 5.10 OOB - IP connectivity test failed (Target: K64F, Host: Windows and Mac).
Expected result
All TEST_APPS should pass.
Actual result
test_cmdline
is skipped andTCPSERVER_ACCEPT
was inconclusive.Versions
python 2.7.15
mbed-cli 1.8.0
icetea 1.0.1
Test result
Complete log file :
mbed-os-oob-icetea.txt
Issue request type
[x] Question
[ ] Enhancement
[x] Bug
The text was updated successfully, but these errors were encountered: