golang/go

net: TestTCPServer/tcp4_:0<-127.0.0.1 failures on Windows with `EOF` (and no other output)

Open

#52,926 opened on May 16, 2022

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Go (19,008 forks)batch import
NeedsInvestigationOS-Windowshelp wanted

Repository metrics

Stars
 (133,883 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

--- FAIL: TestTCPServer (0.02s)
    --- FAIL: TestTCPServer/tcp4_:0<-127.0.0.1 (0.00s)
        server_test.go:113: #19: EOF
FAIL
FAIL	net	54.788s

greplogs -l -e 'FAIL: TestTCPServer .*(?:\n[ ]+.*)* EOF' 2022-05-13T21:00:31-e755a56/windows-amd64-longtest 2019-11-07T02:33:31-198f045/windows-amd64-longtest

Probably a good first step would be to update this test to log more information about what's going on (per https://go.dev/wiki/CodeReviewComments#useful-test-failures), although given the low rate of occurrence it may be a while before we get another hit. 😅

(CC @ianlancetaylor @neild @golang/windows)

Contributor guide

Research direction
Inspect the failing test TestTCPServer, particularly the tcp4:0< 127.0.0.1 subtest, and add more detailed logging to capture the state of the connection when the EOF error occurs, following Go testing best practices.
Tech stack
go
Domain
testing
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Go
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75