-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
net.socket.get_addr_info: frdm_k64f test fails #34923
Comments
@MaureenHelm , @dleach02 , looks like the test is not reliable, but need owner to confirm |
Hake, I'm not able to reproduce this problem. Can you retest with the 2.6 rc1 candidate? *** Booting Zephyr OS build zephyr-v2.5.0-3651-g793e2c1891b4 *** |
I tried this with 2.6.0-rc1
and did not see any issues. |
@jukkar @dleach02
|
Okay. If you connect the K64F to a network then I see the failures Hake is seeing. @jukkar, I'm thinking that this test does want to be connected to a valid network? |
if connect with ethernet cable you will see more tests is runable
but if no ethernet cable, then
|
I have done the tests without any cable connected. This looks like the issue we had earlier when the test uses the board Ethernet controller instead of the fake one which is suppose to be used by the test. This should be an easy fix, I will check if the culprit is that one. |
yeah, this does look like a "self-hosted" test... again. But I don't see where or how to setup for a dummy interface |
If the tests/net/socket/getaddrinfo is run in a board that has Ethernet controller, then it is possible that it will interfere the test if the Ethernet cable is connected. As the test only needs loopback support to run, disable the Ethernet as it is not needed by the test. Fixes zephyrproject-rtos#34923 Signed-off-by: Jukka Rissanen <[email protected]>
The test used loopback interface and as we do not really need Ethernet, then disabling Ethernet will fix the issue. |
If the tests/net/socket/getaddrinfo is run in a board that has Ethernet controller, then it is possible that it will interfere the test if the Ethernet cable is connected. As the test only needs loopback support to run, disable the Ethernet as it is not needed by the test. Fixes #34923 Signed-off-by: Jukka Rissanen <[email protected]>
Describe the bug
below two cases fails, looks like it is not stable enough to all platform
test_getaddrinfo_ok
test_getaddrinfo_cancelled
To Reproduce
Steps to reproduce the behavior:
Expected behavior
all test pass
Impact
addressinfo api call
Logs and console output
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: