Open
Description
Note: This build has runtime assertions enabled. If the same failure was hit in a run without assertions enabled, there should be a similar failure without this message. If there isn't one, then this failure is likely due to an assertion violation or (assertion) timeout.
roachtest.clearrange/zfs/checks=true failed with artifacts on release-25.2 @ b99dcdbbd604a8e710a6a82b9b1125f8ea264028:
(cluster.go:2508).Run: context canceled
(monitor.go:149).Wait: monitor failure: monitor user task failed: t.Fatal() was called
unexpected node event: n6: cockroach process for system interface died (exit code 134)
test artifacts and logs in: /artifacts/clearrange/zfs/checks=true/run_1
Parameters:
arch=amd64
cloud=gce
coverageBuild=false
cpu=16
encrypted=false
fs=zfs
localSSD=true
metamorphicBufferedSender=false
metamorphicLeases=default
runtimeAssertionsBuild=true
ssd=0
Same failure on other branches
- roachtest: clearrange/zfs/checks=true failed #146504 roachtest: clearrange/zfs/checks=true failed [A-storage B-runtime-assertions-enabled C-test-failure O-roachtest O-robot T-storage branch-master release-blocker]
This test on roachdash | Improve this report!
Jira issue: CRDB-50570