-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
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
ccl/streamingccl/streamproducer: TestStreamAddSSTable failed #102523
Comments
did we expect this to be fixed by #102258 ? |
Yeah, but perhaps this |
yeah, the og issue detected 2 leaky goroutines. #97346 |
Fixes cockroachdb#102523 Informs cockroachdb#102286 Informs cockroachdb#86206 Release note: none
Informs cockroachdb#102523 Informs cockroachdb#102286 Informs cockroachdb#86206 Release note: none
jk, there may be a real leak here. investigating further and will skip the test for now. |
102593: c2c: skip and deflake a few unit tests r=benbardin a=msbutler c2c: skip a few unit tests Informs #102523 Informs #102286 Informs #86206 Release note: none c2c: close pgconn with correct context in test infra When a user opens a pgx connection, they pass it a context that must be used to close the connection, else pgx's contextWatcher will run indefinetly on a seperate goroutine. Previously, the `startReplication()` test helper was initializing its own context to open pgx connection, and did not pass this context back to the caller, and consequently, the user would close the connection with the incorrect context, leading to a leaky goroutine. This patch allows the user to pass a context in the startReplication(), preventing the user from closing the connection with the wrong goroutine. Fixes #102523 Release note: None Co-authored-by: Michael Butler <[email protected]>
When a user opens a pgx connection, they pass it a context that must be used to close the connection, else pgx's contextWatcher will run indefinetly on a seperate goroutine. Previously, the `startReplication()` test helper was initializing its own context to open pgx connection, and did not pass this context back to the caller, and consequently, the user would close the connection with the incorrect context, leading to a leaky goroutine. This patch allows the user to pass a context in the startReplication(), preventing the user from closing the connection with the wrong goroutine. Fixes #102523 Release note: None
102593: c2c: skip and deflake a few unit tests r=benbardin a=msbutler c2c: skip a few unit tests Informs cockroachdb#102523 Informs cockroachdb#102286 Informs cockroachdb#86206 Release note: none c2c: close pgconn with correct context in test infra When a user opens a pgx connection, they pass it a context that must be used to close the connection, else pgx's contextWatcher will run indefinetly on a seperate goroutine. Previously, the `startReplication()` test helper was initializing its own context to open pgx connection, and did not pass this context back to the caller, and consequently, the user would close the connection with the incorrect context, leading to a leaky goroutine. This patch allows the user to pass a context in the startReplication(), preventing the user from closing the connection with the wrong goroutine. Fixes cockroachdb#102523 Release note: None Co-authored-by: Michael Butler <[email protected]>
ccl/streamingccl/streamproducer.TestStreamAddSSTable failed with artifacts on master @ 3b1bc872bb4bf8e5eb2ad8790ba8ec781167dd1f:
Parameters:
TAGS=bazel,gss,deadlock
Help
See also: How To Investigate a Go Test Failure (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-27490
The text was updated successfully, but these errors were encountered: