-
Notifications
You must be signed in to change notification settings - Fork 284
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
Execution of io_test (bash_tests.testcases.TestCases) fails on Windows 11 #2781
Comments
I've frequently gotten this error. No real idea why. CI doesn't show it. Maybe firewall is interfering. |
@neheb thanks for the hint, but it's not firewall. It failed after disabling firewall completely. I checked older versions. It worked with the release 0.28.0. It worked running iotest.exe from 0.28.0 with latest test scripts, but not vice versa. So it probably is a change in iotest.exe and I started to look for differences. Perhaps somebody with knowledge what iotest does, can give me a hint where to look at. |
Not at all. edit: try running as Administrator |
Unfortunately, running as Administrator did not help. |
Can you try:
|
I tried it, error is now: What I found now: the code after calling inet_pton in line 205 is not executed, inet_pton returns 1. Looking on https://learn.microsoft.com/en-us/windows/win32/api/ws2tcpip/nf-ws2tcpip-inet_pton and scrolling down to Return value, I found:
As later in the code WSAGetLastError is checked, I tried This was now try-and-error. I am not sure if this change can be the general solution. |
Sounds right. The commit ignores that section. |
If you agree, I will prepare a pull request, also including your change. |
Sure |
When I run the tests with python3 runner.py on my local Windows 11 system, it fails with io_test:
This has a lower priority. As this error occurs even with the original sources from GitHub I ignore it when I test my changes. But I would like to understand it and avoiding this makes it more comfortable to verify my changes.
The text was updated successfully, but these errors were encountered: