Skip to content

fix(harness): disable SeiDB state store on nightly nodes, drop dead ss write-mode #445

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bdchatham merged 1 commit into from
Jun 24, 2026
+10 −6
Merged

fix(harness): disable SeiDB state store on nightly nodes, drop dead ss write-mode #445

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 10 additions & 6 deletions test/integration/harness_test.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,14 +40,18 @@ import (
// DeletionPolicy cascade are the cleanup path.
const runLabelKey = "sei.io/harness-run"

// memiavlStorageConfig is the storage write-mode the load + release suites run
// with — the controller default (cosmos_only) is rejected by the nightly image.
// NOT universal: the major-upgrade suite deliberately omits it (the storage /
// migration path is what that suite tests), so it's applied per-suite via
// spec.storageConfig, never globally.
// memiavlStorageConfig pins storage for the load/release/chaos suites (the
// major-upgrade suite omits it — it tests the migration path). State commitment
// stays on memiavl; the SeiDB state store is disabled because the latest image
// defaults it on for full nodes, and enabling it on a fresh-genesis RPC follower
// deadlocks seid at store-open before it binds listeners. Matches the validators
// (ss-enable=false); FlatKV-migration coverage is unaffected — that's the SC
// layer, not the historical state store. (storage.state_store.write_mode is gone:
// the SS layer has no write-mode field on current sei-chain — EVM routing is the
// evm-split bool — so the old key was a silently-ignored no-op.)
var memiavlStorageConfig = map[string]string{
"storage.state_commit.write_mode": "memiavl_only",
"storage.state_store.write_mode": "memiavl_only",
"storage.state_store.enable": "false",
}

// mergeConfig returns base overlaid with extra; extra wins on key collision.
Expand Down
Loading