sql/importer: TestExportImportBank failed

[cockroach-teamcity]

sql/importer.TestExportImportBank failed on master @ b77653f98b4ce56425f7b0997671d8414051ea54:

=== RUN   TestExportImportBank
    test_log_scope.go:165: test logs captured to: outputs.zip/logTestExportImportBank80965495
    test_log_scope.go:76: use -show-logs to present logs inline
    test_server_shim.go:152: automatically injected a shared process virtual cluster under test; see comment at top of test_server_shim.go for details.
    exportcsv_test.go:141: -- test log scope end --
test logs left over in: outputs.zip/logTestExportImportBank80965495
--- FAIL: TestExportImportBank (476.66s)
=== RUN   TestExportImportBank/null=NULL
    exportcsv_test.go:130: error executing query="IMPORT INTO bank2 CSV DATA ($1) WITH delimiter = '|', nullif = 'NULL'" args=["userfile:/t/TestExportImportBank/null=NULL/*"]: pq: job 1024450313194471425: could not mark as reverting: job 1024450313194471425: with status "running": expected session "0101801d87ef14c2d542d0afe588074c706a05" but found "010180f79889bac6484f23a01397e43091f392"
    panic.go:626: error executing query="DROP TABLE bank2" args=[]: pq: relation "bank2" is offline: importing
    --- FAIL: TestExportImportBank/null=NULL (180.30s)

Parameters:

• attempt=1
• race=true
• run=3
• shard=3

Help

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

This test on roachdash | Improve this report!

Jira issue: CRDB-44957

[yuzefovich]

The symptoms here match what we saw in this failure, and it was in the same config (shared process multi-tenancy, 3 node cluster, and race build).

I wonder whether we want to extend the session liveness expiration in race builds. I'll send a patch for that.