-
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/changefeedccl: TestChangefeedSchemaChangeBackfillCheckpoint failed #119375
Comments
Removing release blocker label since the error message seems to indicate flaky test infra, but Wenyi agreed to investigate. |
ccl/changefeedccl.TestChangefeedSchemaChangeBackfillCheckpoint failed with artifacts on release-23.1 @ 333253387f07fcbfc20697df5556224d44ca86c2:
|
|
Summary of offline discussion: Plan is to add more logs for future debugability and close this issue. |
I suspect this is similar to #120744 and we should consider increasing the batch size here:
|
Previously, TestChangefeedSchemaChangeBackfillCheckpoint could fail when the batch size is too small, leading to a timeout while waiting for initial scan to complete. This patch deflakes TestChangefeedSchemaChangeBackfillCheckpoint by increasing the batch size. Fixes: cockroachdb#119375 Release note: none
ccl/changefeedccl.TestChangefeedSchemaChangeBackfillCheckpoint failed with artifacts on release-23.1 @ bb0d40a1c8334ab6584189c004f358c63bd95aa7:
Parameters:
|
should be fixed by #130966 |
ccl/changefeedccl.TestChangefeedSchemaChangeBackfillCheckpoint failed with artifacts on release-23.1 @ b102a6dd3f49ef7bb92217d005ad890105f84d07:
Parameters:
TAGS=bazel,gss
Help
See also: How To Investigate a Go Test Failure (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-36171
The text was updated successfully, but these errors were encountered: