Skip to content
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.

Sign up for GitHub

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

Jump to bottom

roachtest: cdc/workload/kv100/nodes=5/cpu=16/ranges=100k/server=processor/protocol=rangefeed/format=json/sink=null failed #138120

Open
cockroach-teamcity opened this issue Dec 31, 2024 · 1 comment
Open

roachtest: cdc/workload/kv100/nodes=5/cpu=16/ranges=100k/server=processor/protocol=rangefeed/format=json/sink=null failed #138120

cockroach-teamcity opened this issue Dec 31, 2024 · 1 comment
Assignees
@asg0451
Labels
A-cdc Change Data Capture branch-release-23.2.19-rc C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. P-2 Issues/test failures with a fix SLA of 3 months release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. T-cdc
Milestone
23.2

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Dec 31, 2024 •
edited by cockroach-jira-scripts
Loading

roachtest.cdc/workload/kv100/nodes=5/cpu=16/ranges=100k/server=processor/protocol=rangefeed/format=json/sink=null failed with artifacts on release-23.2.19-rc @ 2bfc920ac073eb944eb7a5918f2632752b289ddd:

(cluster.go:2318).Run: full command output in run_095505.563637758_n7_cockroach-workload-r.log: COMMAND_PROBLEM: exit status 1
test artifacts and logs in: /artifacts/cdc/workload/kv100/nodes=5/cpu=16/ranges=100k/server=processor/protocol=rangefeed/format=json/sink=null/run_1

Parameters:

  • ROACHTEST_arch=amd64
  • ROACHTEST_cloud=gce
  • ROACHTEST_coverageBuild=false
  • ROACHTEST_cpu=16
  • ROACHTEST_encrypted=false
  • ROACHTEST_metamorphicBuild=false
  • ROACHTEST_ssd=0
Help

See: roachtest README

See: How To Investigate (internal)

See: Grafana

/cc @cockroachdb/cdc

This test on roachdash | Improve this report!

Jira issue: CRDB-45905
@cockroach-teamcity cockroach-teamcity added branch-release-23.2.19-rc C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. T-cdc labels Dec 31, 2024
@cockroach-teamcity cockroach-teamcity added this to the 23.2 milestone Dec 31, 2024
@blathers-crl blathers-crl bot added the A-cdc Change Data Capture label Dec 31, 2024
@asg0451 asg0451 removed the release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. label Jan 2, 2025
@asg0451
Copy link
Contributor

asg0451 commented Jan 2, 2025

workload run encountered this error, which i think only happens when nodes crash? worth looking into more.

Error: ERROR: result is ambiguous: unable to determine whether command was applied via snapshot (SQLSTATE 40003)

@asg0451 asg0451 added the release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. label Jan 2, 2025
@asg0451 asg0451 self-assigned this Jan 2, 2025
@exalate-issue-sync exalate-issue-sync bot added the P-2 Issues/test failures with a fix SLA of 3 months label Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@asg0451 asg0451

Labels
A-cdc Change Data Capture branch-release-23.2.19-rc C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. P-2 Issues/test failures with a fix SLA of 3 months release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. T-cdc
Projects
None yet
Milestone
23.2
Development

No branches or pull requests
2 participants
@asg0451 @cockroach-teamcity