UT in package `net` is always killed with `-race`
Open
Nobody has claimed this yet.
unit test
- Dominant language
- Go
- Stars
- 73
- Forks
- 41
- Avg merge
- 21h 3m
- Merged PRs (30d)
- 21
Description
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
Add -race to run go test in CI.
2. What did you expect to see? (Required)
No error
3. What did you see instead (Required)
The package net is always killed, even if I added a long timeout to go test.
It only runs for 36s, so it definitely not because of timeout (maybe because of OOM?):
signal: killed
FAIL github.com/pingcap/tiproxy/pkg/proxy/net 36.001s
4. What is your version? (Required)
master
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the Go tests for pkg/proxy/net with -race, using the issue's 36-second failure as the reproduction point. Check the CI run linked in the report and determine whether the kill is caused by resource usage rather than the test timeout. Done means the package test completes successfully with -race in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100