ccl/kvccl/kvtenantccl: TestTenantUpgradeInterlock failed #98986
Description
ccl/kvccl/kvtenantccl.TestTenantUpgradeInterlock failed with artifacts on master @ 1cf75095871a9df935c036c674783dca73a02134:
Fatal error:
panic: test timed out after 4m55s
Stack:
goroutine 378755 [running]:
testing.(*M).startAlarm.func1()
GOROOT/src/testing/testing.go:2036 +0x88
created by time.goFunc
GOROOT/src/time/sleep.go:176 +0x38
Log preceding fatal error
=== RUN TestTenantUpgradeInterlock
test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/416c130b9e53a570f2915b8546e7d23c/logTestTenantUpgradeInterlock3671635970
test_log_scope.go:79: use -show-logs to present logs inline
=== RUN TestTenantUpgradeInterlock/current_binary_version_pause_after_write_to_settings_table
tenant_upgrade_test.go:525: upgrade interlock test: running variant "current binary version", configuration: "pause after write to settings table"
=== RUN TestTenantUpgradeInterlock/current_binary_version_pause_after_fence_RPC
tenant_upgrade_test.go:525: upgrade interlock test: running variant "current binary version", configuration: "pause after fence RPC"
=== RUN TestTenantUpgradeInterlock/current_binary_version_pause_after_migration
tenant_upgrade_test.go:525: upgrade interlock test: running variant "current binary version", configuration: "pause after migration"
=== RUN TestTenantUpgradeInterlock/lagging_binary_version_pause_after_migration
tenant_upgrade_test.go:525: upgrade interlock test: running variant "lagging binary version", configuration: "pause after migration"
=== RUN TestTenantUpgradeInterlock/lagging_binary_version_pause_after_second_check_of_instances
tenant_upgrade_test.go:525: upgrade interlock test: running variant "lagging binary version", configuration: "pause after second check of instances"
=== RUN TestTenantUpgradeInterlock/lagging_binary_version_pause_after_version_bump_RPC
tenant_upgrade_test.go:525: upgrade interlock test: running variant "lagging binary version", configuration: "pause after version bump RPC"
This test on roachdash | Improve this report!
Jira issue: CRDB-25639
Epic CRDB-27931