We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
net
-race
Please answer these questions before submitting your issue. Thanks!
Add -race to run go test in CI.
go test
No error
The package net is always killed, even if I added a long timeout to go test.
e.g. https://do.pingcap.net/jenkins/blue/organizations/jenkins/pingcap%2Ftiproxy%2Fghpr_unit_test/detail/ghpr_unit_test/29/pipeline
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
master
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
Add
-race
to rungo 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 togo test
.e.g. https://do.pingcap.net/jenkins/blue/organizations/jenkins/pingcap%2Ftiproxy%2Fghpr_unit_test/detail/ghpr_unit_test/29/pipeline
It only runs for 36s, so it definitely not because of timeout (maybe because of OOM?):
4. What is your version? (Required)
master
The text was updated successfully, but these errors were encountered: