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: acceptance/c2c failed #99552

Closed
cockroach-teamcity opened this issue Mar 25, 2023 · 7 comments
Closed

roachtest: acceptance/c2c failed #99552

cockroach-teamcity opened this issue Mar 25, 2023 · 7 comments
Assignees
Labels
branch-release-23.1 Used to mark GA and release blockers, technical advisories, and bugs for 23.1 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 Mar 25, 2023

roachtest.acceptance/c2c failed with artifacts on release-23.1 @ f351747ed97862fc037717cadec23f18073fb6be:

test artifacts and logs in: /artifacts/acceptance/c2c/run_1
(cluster_to_cluster.go:619).runAcceptanceClusterReplication: acceptance tests should only run on a local cluster

Parameters: ROACHTEST_cloud=gce , ROACHTEST_cpu=4 , ROACHTEST_encrypted=false , ROACHTEST_fs=ext4 , ROACHTEST_localSSD=true , ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

/cc @cockroachdb/disaster-recovery

This test on roachdash | Improve this report!

Jira issue: CRDB-25925

@cockroach-teamcity cockroach-teamcity added branch-release-23.1 Used to mark GA and release blockers, technical advisories, and bugs for 23.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. labels Mar 25, 2023
@cockroach-teamcity cockroach-teamcity added this to the 23.1 milestone Mar 25, 2023
@cockroach-teamcity
Copy link
Member Author

roachtest.acceptance/c2c failed with artifacts on release-23.1 @ b995ddff53ee95a30537a366c6cd8e0e13fcee79:

test artifacts and logs in: /artifacts/acceptance/c2c/run_1
(cluster_to_cluster.go:619).runAcceptanceClusterReplication: acceptance tests should only run on a local cluster

Parameters: ROACHTEST_cloud=gce , ROACHTEST_cpu=4 , ROACHTEST_encrypted=false , ROACHTEST_fs=ext4 , ROACHTEST_localSSD=true , ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

Same failure on other branches

This test on roachdash | Improve this report!

@stevendanna
Copy link
Collaborator

@msbutler :D Looks like we forgot this would run as part of the nightly as well. We should probably change that fatal to something that just skips.

@stevendanna stevendanna removed the release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. label Mar 26, 2023
@stevendanna
Copy link
Collaborator

Ah, you already did beat me to it: #99574

@cockroach-teamcity
Copy link
Member Author

roachtest.acceptance/c2c failed with artifacts on release-23.1 @ b995ddff53ee95a30537a366c6cd8e0e13fcee79:

test artifacts and logs in: /artifacts/acceptance/c2c/run_1
(cluster_to_cluster.go:619).runAcceptanceClusterReplication: acceptance tests should only run on a local cluster

Parameters: ROACHTEST_cloud=gce , ROACHTEST_cpu=4 , ROACHTEST_encrypted=false , ROACHTEST_fs=ext4 , ROACHTEST_localSSD=true , ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

Same failure on other branches

This test on roachdash | Improve this report!

@cockroach-teamcity
Copy link
Member Author

roachtest.acceptance/c2c failed with artifacts on release-23.1 @ 186218edb86b5974501b2976cfd0704d4d6d1beb:

test artifacts and logs in: /artifacts/acceptance/c2c/run_1
(cluster_to_cluster.go:619).runAcceptanceClusterReplication: acceptance tests should only run on a local cluster

Parameters: ROACHTEST_cloud=gce , ROACHTEST_cpu=4 , ROACHTEST_encrypted=false , ROACHTEST_fs=ext4 , ROACHTEST_localSSD=true , ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

Same failure on other branches

This test on roachdash | Improve this report!

@cockroach-teamcity
Copy link
Member Author

roachtest.acceptance/c2c failed with artifacts on release-23.1 @ 3551dc089ac3efcb3772df2109164dcb01e79d8f:

test artifacts and logs in: /artifacts/acceptance/c2c/run_1
(cluster_to_cluster.go:619).runAcceptanceClusterReplication: acceptance tests should only run on a local cluster

Parameters: ROACHTEST_cloud=gce , ROACHTEST_cpu=4 , ROACHTEST_encrypted=false , ROACHTEST_fs=ext4 , ROACHTEST_localSSD=true , ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

Same failure on other branches

This test on roachdash | Improve this report!

@msbutler
Copy link
Collaborator

FIxed by #99818

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch-release-23.1 Used to mark GA and release blockers, technical advisories, and bugs for 23.1 C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. T-disaster-recovery
Projects
No open projects
Archived in project
Development

No branches or pull requests

3 participants