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: tpcc/mixed-headroom/multiple-upgrades/n5cpu16 failed #97582

Closed
cockroach-teamcity opened this issue Feb 23, 2023 · 1 comment
Closed

roachtest: tpcc/mixed-headroom/multiple-upgrades/n5cpu16 failed #97582

cockroach-teamcity opened this issue Feb 23, 2023 · 1 comment
Labels
branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. T-testeng TestEng Team
Milestone
23.1

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Feb 23, 2023 •
edited by cockroach-jira-scripts
Loading

roachtest.tpcc/mixed-headroom/multiple-upgrades/n5cpu16 failed with artifacts on master @ e028ce5b14505dfd17ef8b13001c0ab8ac811e3c:

test artifacts and logs in: /artifacts/tpcc/mixed-headroom/multiple-upgrades/n5cpu16/run_1
(cluster.go:1883).Start: COMMAND_PROBLEM: ssh verbose log retained in ssh_182606.752547688_n1_COCKROACHCONNECTTIME.log: exit status 127

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

Help

See: roachtest README

See: How To Investigate (internal)

/cc @cockroachdb/test-eng

This test on roachdash | Improve this report!

Jira issue: CRDB-24769
@cockroach-teamcity cockroach-teamcity added branch-master Failures and bugs on the master branch. 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 Feb 23, 2023
@cockroach-teamcity cockroach-teamcity added this to the 23.1 milestone Feb 23, 2023
@blathers-crl blathers-crl bot added the T-testeng TestEng Team label Feb 23, 2023
@renatolabs renatolabs mentioned this issue Feb 23, 2023
Merged
@renatolabs renatolabs removed the release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. label Feb 23, 2023
craig bot pushed a commit that referenced this issue Feb 24, 2023
@msbutler
Merge #97581
973181a 
97581: roachtest: always use active node in backup schedule injection r=renatolabs a=msbutler

Previously, the schedule backup cmd injection on Start() would always run on the first node on the cluster, but if that node were not available, the cmd would fail. This patch ensures the injection runs on a node that was just started.

Fixes #97558, #97582, #97548, #97562 #97565 #97561

Release note: None

Co-authored-by: Michael Butler <[email protected]>
@msbutler
Copy link
Collaborator

fixed by #97581

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. T-testeng TestEng Team
Projects
None yet
Milestone
23.1
Development

No branches or pull requests
3 participants
@cockroach-teamcity @msbutler @renatolabs