basalt-26.3: roachtest: schema_change_workload_failure failed

**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.schema_change_workload_failure [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_Roachtests_GreenRoachtestNightlyGcePrivateBasaltBazel/21512126?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_Roachtests_GreenRoachtestNightlyGcePrivateBasaltBazel/21512126?buildTab=artifacts#/backup-restore/small-ranges) on basalt-26.3 @ [ce03c201a58400d4ce8a20ad7b4b27b87ffa5225](https://github.com/cockroachdb/cockroach/commits/ce03c201a58400d4ce8a20ad7b4b27b87ffa5225):

Failed with:

```
test backup-restore/small-ranges failed: (test_runner.go:2762).func1: task ``run-schemachange`` returned error: schema change workload failed: full command output in run_161944.687286513_n4_COCKROACHRANDOMSEED3.log: COMMAND_PROBLEM: exit status 134 [owner=sql-foundations]
(monitor.go:267).Wait: monitor failure: error waiting for job 1209379575587012609 to finish: context canceled
test artifacts and logs in: /artifacts/backup-restore/small-ranges/run_1
```
Cluster Node to Ip Mapping:
| Node | Public IP | Private IP |
| --- | --- | --- |
| teamcity-21512126-1789140791-27-n4cpu4-0001 | | 10.91.98.27 |
| teamcity-21512126-1789140791-27-n4cpu4-0002 | | 10.91.98.44 |
| teamcity-21512126-1789140791-27-n4cpu4-0003 | | 10.91.98.43 |
| teamcity-21512126-1789140791-27-n4cpu4-0004 | | 10.91.98.63 |

Parameters:
- MetamorphicBasaltMultiAZ=false
- arch=amd64
- cloud=gce
- coverageBuild=false
- cpu=4
- diskCount=0
- encrypted=false
- fs=ext4
- localSSD=true
- metamorphicDRPC=true
- metamorphicWriteBuffering=true
- runtimeAssertionsBuild=true
- storageNodesVersion=v0.1.19-nightly.20260911
Help

See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)

See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)

See: [Grafana](https://go.crdb.dev/roachtest-grafana/teamcity-21512126/backup-restore-small-ranges/1789142923315/1789144715952)

_Logs were not uploaded to Datadog_

/cc @cockroachlabs/sql-foundations

[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*schema_change_workload_failure.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)

Start with the failing run_161944.687286513_n4_COCKROACHRANDOMSEED3.log in the backup-restore/small-ranges artifacts and the roachtest README. Trace the run-schemachange failure through test_runner.go:2762, then use the logs and Grafana link to identify the cause; done means the schema_change_workload_failure test passes reliably.

Written by the indexing model from the issue text.