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.

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

roachtest: c2c/BulkOps/short failed #123175

Open
cockroach-teamcity opened this issue Apr 27, 2024 · 1 comment
Open

roachtest: c2c/BulkOps/short failed #123175

cockroach-teamcity opened this issue Apr 27, 2024 · 1 comment
Assignees
Labels
C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. T-disaster-recovery
Milestone

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Apr 27, 2024

roachtest.c2c/BulkOps/short failed with artifacts on release-24.1 @ 3f3127b8b592b9c63df76e47cb9f0a3b47357f62:

(assertions.go:333).Fail: 
	Error Trace:	github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/cluster_to_cluster.go:861
	            				github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/cluster_to_cluster.go:962
	            				github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/cluster_to_cluster.go:1271
	            				main/pkg/cmd/roachtest/monitor.go:120
	            				golang.org/x/sync/errgroup/external/org_golang_x_sync/errgroup/errgroup.go:78
	            				src/runtime/asm_amd64.s:1695
	Error:      	"1" is not greater than "1"
	Test:       	c2c/BulkOps/short
	Messages:   	only 1 src node participating
(require.go:609).Greater: FailNow called
(monitor.go:154).Wait: monitor failure: monitor user task failed: t.Fatal() was called
test artifacts and logs in: /artifacts/c2c/BulkOps/short/run_1

Parameters:

  • ROACHTEST_arch=amd64
  • ROACHTEST_cloud=gce
  • ROACHTEST_coverageBuild=false
  • ROACHTEST_cpu=8
  • ROACHTEST_encrypted=false
  • ROACHTEST_fs=ext4
  • ROACHTEST_localSSD=false
  • ROACHTEST_metamorphicBuild=false
  • ROACHTEST_ssd=0
Help

See: roachtest README

See: How To Investigate (internal)

See: Grafana

/cc @cockroachdb/disaster-recovery

This test on roachdash | Improve this report!

Jira issue: CRDB-38223

@cockroach-teamcity cockroach-teamcity added branch-release-24.1 Used to mark GA and release blockers and technical advisories for 24.1 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-disaster-recovery labels Apr 27, 2024
@cockroach-teamcity cockroach-teamcity added this to the 24.1 milestone Apr 27, 2024
@msbutler msbutler removed the release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. label Apr 29, 2024
@msbutler
Copy link
Collaborator

likely flaking due to the the bulk ops planner. removing release blocker

@msbutler msbutler removed the branch-release-24.1 Used to mark GA and release blockers and technical advisories for 24.1 label Apr 30, 2024
msbutler added a commit to msbutler/cockroach that referenced this issue May 1, 2024
msbutler added a commit to msbutler/cockroach that referenced this issue May 1, 2024
msbutler added a commit to msbutler/cockroach that referenced this issue May 9, 2024
msbutler added a commit to msbutler/cockroach that referenced this issue May 10, 2024
msbutler added a commit to msbutler/cockroach that referenced this issue May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. T-disaster-recovery
Development

No branches or pull requests

2 participants