basalt-26.3.2-rc-20260913: ccl/serverccl: TestExecSQL failed

ccl/serverccl.TestExecSQL [failed](https://mesolite.cluster.engflow.com/invocations/default/11909b1c-46c9-4083-b604-1fc5eb600b93?testReportRun=2&testReportShard=1&testReportAttempt=1#targets-Ly9wa2cvY2NsL3NlcnZlcmNjbDpzZXJ2ZXJjY2xfdGVzdA==) on basalt-26.3.2-rc-20260913 @ [c6a822fb5ec0b622c713fccacb82159d1b60bbcd](https://github.com/cockroachdb/cockroach/commits/c6a822fb5ec0b622c713fccacb82159d1b60bbcd):

```
=== RUN TestExecSQL
test_log_scope.go:172: test logs captured to: outputs.zip/logTestExecSQL3114518689
test_log_scope.go:82: use -show-logs to present logs inline
panic.go:694: -- test log scope end --
--- FAIL: TestExecSQL (38.11s)
=== RUN TestExecSQL/sql_drop_table
datadriven.go:263:
testdata/api_v2_sql:473:
sql admin
{
"database": "mydb",
"execute": true,
"statements": [
{"sql": "DROP TABLE bar"}
]
}
output didn't match expected:
@@ -1,6 +1,17 @@
{
+ "error": {
+ "code": "XXUUU",
+ "hint": "The job may not have succeeded.",
+ "message": "operation \"run-sql-via-api\" timed out after 5.013s (given timeout 5s): job 1210479523527294977 could not be loaded: txn exec: context deadline exceeded",
+ "severity": "ERROR",
+ "source": {
+ "file": "txn.go",
+ "function": "exec",
+ "line": 1188
+ }
+ },
"execution": {
"txn_results": [
{
"columns": [
{
--- FAIL: TestExecSQL/sql_drop_table (5.15s)
```

Parameters:
- attempt=1
- race=true
- run=2
- shard=1
Help

See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)

Same failure on other branches

- #174999 ccl/serverccl: TestExecSQL failed [C-test-failure O-robot T-observability branch-master release-blocker]

/cc @cockroachlabs/obs-prs

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

Start with ccl/serverccl.TestExecSQL and the testdata/api_v2_sql:473 case for sql_drop_table. Reproduce the failure using the linked test report and logs, then investigate the 5-second run-sql-via-api timeout and context deadline exceeded error. Done means TestExecSQL passes with the expected output.

Written by the indexing model from the issue text.