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/kv0 failed #130066

Closed
cockroach-teamcity opened this issue Sep 4, 2024 · 3 comments
Closed

roachtest: c2c/kv0 failed #130066

cockroach-teamcity opened this issue Sep 4, 2024 · 3 comments
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-testeng TestEng Team
Milestone

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Sep 4, 2024

roachtest.c2c/kv0 failed with artifacts on release-23.1 @ 023468c57cfabd42d811906cabaf0ccfa4788151:

(cluster.go:2042).Start: COMMAND_PROBLEM: exit status 1
test artifacts and logs in: /artifacts/c2c/kv0/cpu_arch=arm64/run_1

Parameters:

  • ROACHTEST_arch=arm64
  • ROACHTEST_cloud=aws
  • 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)

Grafana is not yet available for aws clusters

Same failure on other branches

/cc @cockroachdb/disaster-recovery

This test on roachdash | Improve this report!

Jira issue: CRDB-41859

@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. T-disaster-recovery labels Sep 4, 2024
@cockroach-teamcity cockroach-teamcity added this to the 23.1 milestone Sep 4, 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 Sep 9, 2024
@msbutler
Copy link
Collaborator

msbutler commented Sep 9, 2024

looks like roachprod start failed, according to failure_1.log, on node 2

Node 2's logs suggest it fataled due to disk stall. Passing this over to test-eng, which may know if we can close this as a one time flake.

I240904 05:53:28.295500 72 1@cli/start.go:1528 ⋮ [T1,n?] 19 +Node will now attempt to join a running cluster, or wait for `cockroach init`.
I240904 05:53:28.295500 72 1@cli/start.go:1528 ⋮ [T1,n?] 19 +Client connections will be accepted after this completes successfully.
I240904 05:53:28.295500 72 1@cli/start.go:1528 ⋮ [T1,n?] 19 +Check the log file(s) for progress.
W240904 05:53:38.974805 171 1@util/log/file.go:274 ⋮ [-] 20  disk slowness detected: unable to sync log files within 10s

@msbutler msbutler removed their assignment Sep 9, 2024
@msbutler msbutler added T-testeng TestEng Team and removed T-disaster-recovery labels Sep 9, 2024
Copy link

blathers-crl bot commented Sep 9, 2024

cc @cockroachdb/test-eng

@renatolabs
Copy link
Collaborator

n2 definitely had a disk stall, it crashed shortly after that log line was printed. Given that there was nothing happening in this test (workload wasn't running yet), it's unlikely this is an issue related to CRDB, so I'm closing.

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-testeng TestEng Team
Projects
None yet
Development

No branches or pull requests

3 participants