From 01056d1448070fc3c60a68a181939d40b19aa5b8 Mon Sep 17 00:00:00 2001 From: bdchatham Date: Wed, 24 Jun 2026 13:02:34 -0700 Subject: [PATCH] fix(harness): unique chain id for the major-upgrade suite too #446 wired runChainID into the load/release/chaos suites but missed TestChainUpgrade, which provisions a 4-validator chain on a static SEI_CHAIN_ID ("upg") and is therefore exposed to the same stale-genesis halt on any same-id collision (back-to-back run, or SIGKILL leaving genesis behind). Its own doc already calls SEI_CHAIN_ID "(base)"; this makes the code match. Completes the per-run unique chain id across all four suites. Co-Authored-By: Claude Opus 4.8 --- test/integration/upgrade_test.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/integration/upgrade_test.go b/test/integration/upgrade_test.go index 08e463a..9748636 100644 --- a/test/integration/upgrade_test.go +++ b/test/integration/upgrade_test.go @@ -93,7 +93,7 @@ const restUnreachable = "REST unreachable / non-200" // UPGRADE_HEIGHT_DELTA [optional]. Run with -test.timeout 0 (see TestBenchmark). func TestChainUpgrade(t *testing.T) { requireCluster(t) - chainID := mustEnv(t, "SEI_CHAIN_ID") + chainID := runChainID(mustEnv(t, "SEI_CHAIN_ID")) preImage := mustEnv(t, "SEID_IMAGE") postImage := mustEnv(t, "SEID_UPGRADE_IMAGE") upgradeName := mustEnv(t, "SEI_UPGRADE_NAME")