sql/stmtdiagnostics: TestDiagnosticsRequest failed

[cockroach-teamcity]

sql/stmtdiagnostics.TestDiagnosticsRequest failed with artifacts on release-23.2 @ d50f2d0b344d08252f40b95b254a5106d45f3fcd:

=== RUN   TestDiagnosticsRequest
    test_log_scope.go:170: test logs captured to: /artifacts/tmp/_tmp/cb4e70d2cc4a901d2a7689654ffd0100/logTestDiagnosticsRequest1113183579
    test_log_scope.go:81: use -show-logs to present logs inline
    test_server_shim.go:159: automatically injected an external process virtual cluster under test; see comment at top of test_server_shim.go for details.
    statement_diagnostics_test.go:540: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/cb4e70d2cc4a901d2a7689654ffd0100/logTestDiagnosticsRequest1113183579
--- FAIL: TestDiagnosticsRequest (114.84s)
=== RUN   TestDiagnosticsRequest/plan-gist_matching
    sql_runner.go:87: error executing query="INSERT INTO large SELECT 2 FROM generate_series(1, 10000);" args=[]: dial tcp 127.0.0.1:44911: connect: connection refused
    --- FAIL: TestDiagnosticsRequest/plan-gist_matching (99.93s)

Parameters:

• TAGS=bazel,gss
• stress=true

Help

See also: How To Investigate a Go Test Failure (internal)

This test on roachdash | Improve this report!

Jira issue: CRDB-39036

[yuzefovich]

We haven't seen this particular failure mode in this test before. I'll close this as infra flake due to overload.