Some tests fail on K64F & ESP8x about esp8266-driver

[geky]

I don't actually want to merge https://github.com/ARMmbed/esp8266-driver/tree/g-connect-retries

I'd consider retries at this level to be an issue with the test framework, so I'll move them there.

[geky]

Hi @MarceloSalazar, thanks for the test log, that helps a bunch.

It looks like the esp8266 can't establish a connection to your host PC. For those three tests, the esp8266 is supposed to connect to your computer, but the logs are showing that you can't.

Is it possible that there is something preventing the device and PC from talking to each other? Maybe your firewall is getting in the way?

[MarceloSalazar]

Thanks @geky, you seem to be right, I've moved to a PC with Windows 10 and things have improve a bit. All tests usually pass (w/wo DEBUG), but sometimes random tests fail. See log with lots of tests:
lots_of_tests.txt

Also, the connectivity test sometimes fails when running it alone multiple times (with DEBUG enabled), might be related to previous report. See log:
tests-net-conn_fail.txt

I don't know whether this might be caused by the ESP8x fw, or the tests itself, but it would be great to be able to consistently have all tests passing at some point. Let me know if you need more info/help to do more testing.

[geky]

Ah! that's good new. In the new results, it looks like the esp8266 just isn't able to connect to the wifi occasionally. We can add some retry logic to the tests for this.

[geky]

Hi @MarceloSalazar, are you able to try this branch and see if it still shows the intermitent failures?
https://github.com/ARMmbed/esp8266-driver/tree/g-connect-retries

[MarceloSalazar]

@geky I've been running the tests based on your branch the whole day.
The tests run in the morning are very unreliable (half of them fail), whether the ones run in the afternoon consistently pass all the time (more than 20 cycles completed!).
I suspect this might be related to the wifi network infrastructure, but cannot really say.
I'd be happy if you merge the branch and then close this issue.

[ciarmcom]

ARM Internal Ref: MBOTRIAGE-502

[cmonr]

Closing due to inactivity.