-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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/streamingest: TestAlterTenantUpdateExistingCutoverTime failed #124553
Labels
branch-master
Failures on the master branch.
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
C-test-failure
Broken test (automatically or manually discovered).
O-robot
Originated from a bot.
P-1
Issues/test failures with a fix SLA of 1 month
release-blocker
Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked.
T-kv
KV Team
Projects
Comments
This is a data race that appears to be happening inside an admin split. From the stack it doesn't look like it is actually in the ingest code. |
The write seems problematic, but still benign.
Possibly showing up now due to ba13697, which added the batch information cc @lyang24 Details
|
would a shallow copy of batch fix this? let me send a patch |
lyang24
added a commit
to lyang24/cockroach
that referenced
this issue
May 23, 2024
This avoids a data race on tryBumpBatchTimestamp, which was fallout from the new logging introduced in ba13697. Fixes: cockroachdb#124553 Release note: None
lyang24
added a commit
to lyang24/cockroach
that referenced
this issue
May 23, 2024
This avoids a data race on tryBumpBatchTimestamp, which was fallout from the new logging introduced in ba13697. Fixes: cockroachdb#124553 Release note: None
lyang24
added a commit
to lyang24/cockroach
that referenced
this issue
May 25, 2024
This avoids a data race on tryBumpBatchTimestamp, which was fallout from the new logging introduced in ba13697. Fixes: cockroachdb#124553 Release note: None
lyang24
added a commit
to lyang24/cockroach
that referenced
this issue
May 25, 2024
This avoids a data race on tryBumpBatchTimestamp, which was fallout from the new logging introduced in ba13697. Fixes: cockroachdb#124553 Release note: None
lyang24
added a commit
to lyang24/cockroach
that referenced
this issue
May 28, 2024
This avoids a data race on tryBumpBatchTimestamp, which was fallout from the new logging introduced in ba13697. Fixes: cockroachdb#124553 Release note: None
lyang24
added a commit
to lyang24/cockroach
that referenced
this issue
Jun 11, 2024
This avoids a data race on tryBumpBatchTimestamp, which was fallout from the new logging introduced in ba13697. Fixes: cockroachdb#124553 Release note: None
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
branch-master
Failures on the master branch.
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
C-test-failure
Broken test (automatically or manually discovered).
O-robot
Originated from a bot.
P-1
Issues/test failures with a fix SLA of 1 month
release-blocker
Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked.
T-kv
KV Team
ccl/streamingccl/streamingest.TestAlterTenantUpdateExistingCutoverTime failed on master @ 8156d095961d7271df61fe2e2f716ef072bc5f96:
Parameters:
attempt=1
race=true
run=2
shard=4
Help
See also: How To Investigate a Go Test Failure (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-38953
The text was updated successfully, but these errors were encountered: