forks/go-ethereum
1
0
Fork 1
mirror of https://github.com/ethereum/go-ethereum.git synced 2026-05-24 08:49:29 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

rpc: tolerate Windows close-error in websocket read-limit test

Browse source 
On Windows the read-limit violation surfaces as "wsarecv: An existing
connection was forcibly closed by the remote host" instead of "connection
reset by peer", causing TestServerWebsocketReadLimit to flake. Accept
"forcibly closed" as another expected error string.
This commit is contained in:
rayoo 2026-05-20 11:13:54 +08:00
parent 50ae34c1d8
commit e89b82ea9b
1 changed files with 2 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
rpc/server_test.go
View file

@ -274,7 +274,8 @@ func TestServerWebsocketReadLimit(t *testing.T) {
} else if !errors.Is(err, websocket.ErrReadLimit) && } else if !errors.Is(err, websocket.ErrReadLimit) &&
!strings.Contains(strings.ToLower(err.Error()), "1009") && !strings.Contains(strings.ToLower(err.Error()), "1009") &&
!strings.Contains(strings.ToLower(err.Error()), "message too big") && !strings.Contains(strings.ToLower(err.Error()), "message too big") &&
!strings.Contains(strings.ToLower(err.Error()), "connection reset by peer") { !strings.Contains(strings.ToLower(err.Error()), "connection reset by peer") &&
!strings.Contains(strings.ToLower(err.Error()), "forcibly closed") {
// Not the error we expect from exceeding the message size limit. // Not the error we expect from exceeding the message size limit.
t.Fatalf("unexpected error for read limit violation: %v", err) t.Fatalf("unexpected error for read limit violation: %v", err)
} }