You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When doing stress test, e.g., TESTS=server STRESS_TEST_TIMES=500 make test, the test might failed after hundreds of tests.
The error is bind failed (address in use), which is because of the old socket that listening in the port isn't closed.
To close a listening socket, we first cancel all ongoing accept io-uring request, however, the request seems lost when doing stress test. e.g., we try to cancel 10 requests, but only 9 requests were canceled, which left one request to lose.
When I add log to locate this bug, I find it's hard to reproduce the bug if I add many logs in io-uring operation.
I thought it's might because of the third crate io-uring crate, since our io-uring crate is outdated.
When doing stress test, e.g.,
TESTS=server STRESS_TEST_TIMES=500 make test
, the test might failed after hundreds of tests.The error is bind failed (address in use), which is because of the old socket that listening in the port isn't closed.
To close a listening socket, we first cancel all ongoing accept io-uring request, however, the request seems lost when doing stress test. e.g., we try to cancel 10 requests, but only 9 requests were canceled, which left one request to lose.
When I add log to locate this bug, I find it's hard to reproduce the bug if I add many logs in io-uring operation.
I thought it's might because of the third crate
io-uring
crate, since ourio-uring
crate is outdated.And I try to update the
io-uring
crate (The interface of io-uring crate changed a lot), and then I meet more bugs...... (The code is in https://github.com/ShuochengWang/io-uring/tree/sgx and https://github.com/ShuochengWang/ngo/tree/dev-network9)The log of this bug:
The text was updated successfully, but these errors were encountered: