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.
(jepsen.go:118).initJepsen: cluster.GitClone: full command output in run_120843.120041084_n6_bash-e-c-if-test-d-m.log: COMMAND_PROBLEM: exit status 128
test artifacts and logs in: /artifacts/jepsen/sequential/split/run_1
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.jepsen/sequential/split failed with artifacts on release-24.3 @ a8238bebce529c9fbd1c795a246fbcc7f96135e4:
Parameters:
arch=amd64
cloud=gce
coverageBuild=false
cpu=4
encrypted=false
runtimeAssertionsBuild=true
ssd=0
Help
See: roachtest README
See: How To Investigate (internal)
See: Grafana
/cc @cockroachdb/test-engThis test on roachdash | Improve this report!
Jira issue: CRDB-44775