-
Notifications
You must be signed in to change notification settings - Fork 6
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
UT occasionally failed #19
Comments
I see |
I've added the call stack to fail in #20 , to be reproduced. |
I suppose it's because the test result is printed with my patch applied which adds code lines to server.rs #18 |
I re-ran the test on the latest main branch. Please check out the error message
|
test response::tests::test_set_server ... ok
test response::tests::test_status_code ... ok
test response::tests::test_write_response ... ok
test router::tests::test_create_router ... ok
test router::tests::test_handle_http_request ... ok
test connection::tests::test_try_read_split_ending ... ok
test server::tests::test_connection_size_limit_exceeded ... ok
test server::tests::test_set_payload_size ... ok
test connection::tests::test_try_read_long_headers ... ok
test server::tests::test_wait_in_flight_responses ... FAILED
test server::tests::test_wait_concurrent_connections ... ok
test server::tests::test_wait_many_connections ... ok
test server::tests::test_wait_one_connection ... ok
test server::tests::test_wait_one_fd_connection ... ok
test server::tests::test_wait_parse_error ... ok
test server::tests::test_large_payload ... ok
test server::tests::test_wait_expect_connection ... ok
failures:
---- server::tests::test_wait_in_flight_responses stdout ----
thread 'server::tests::test_wait_in_flight_responses' panicked at 'called
Result::unwrap()
on anErr
value: Underflow', src/server.rs:1134:14note: run with
RUST_BACKTRACE=1
environment variable to display a backtracefailures:
server::tests::test_wait_in_flight_responses
The text was updated successfully, but these errors were encountered: