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
While the test response::stream::sse::sse_tests::test_heartbeat is repeated multiple times in the test garnish and has been always successful, I got now one time an assertion failed.
Is anybody of you using EventStream SSE of Rocket and has seen any inexplicable outputs??!!
The result of the test looks like a memory corruption or a race in setting memory boundaries:
cd core/lib
c=0; rc=0 ;while [ "$rc"-eq 0 ] ;do cargo +stable test response::stream::sse::sse_tests::test_heartbeat ; rc=$?; c=$((c+1));done;echo"Failed after run $c"
Failed after run 7 or Failed after run 79.
But fails always if you try it often enough.
Expected Behavior
Test response::stream::sse::sse_tests::test_heartbeat should never fail.
Description
While the test
response::stream::sse::sse_tests::test_heartbeat
is repeated multiple times in the test garnish and has been always successful, I got now one time an assertion failed.Is anybody of you using EventStream SSE of Rocket and has seen any inexplicable outputs??!!
The result of the test looks like a memory corruption or a race in setting memory boundaries:
https://github.com/kolbma/Rocket/blob/e365ab9ba423cf90864749318b548731ee9dc8d3/core/lib/src/response/stream/sse.rs#L792-L795
To Reproduce
Failed after run 7 or Failed after run 79.
But fails always if you try it often enough.
Expected Behavior
Test
response::stream::sse::sse_tests::test_heartbeat
should never fail.Environment:
Additional Context
Need to stress test this some more.
The text was updated successfully, but these errors were encountered: