ci: probe Autobahn Chain Operation Test (CON-256)#3492
Draft
wen-coding wants to merge 4 commits into
Draft
Conversation
Mirror the existing CometBFT "Chain Operation Test" matrix entry with
the standard Autobahn env (AUTOBAHN=true GIGA_EXECUTOR=true
GIGA_STORAGE=true GIGA_OCC=true) and the same script list. Goal is to
see which sub-step Autobahn breaks on:
- snapshot_operation.yaml — exercises snapshot-based state import
- statesync_operation.yaml — expected to fail (Autobahn doesn't drive
CometBFT-style state sync today)
- verify_statesync_flatkv_digest.sh
- verify_cross_validator_flatkv_digest.sh
This is a draft probe; once CI tells us exactly which steps fail under
Autobahn, the script list can be carved down to the working subset (or
the entry deleted if nothing useful runs without Autobahn state sync).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest Buf updates on your PR. Results from workflow Buf / buf (pull_request).
|
…ster The Chain Operation Test runs an extra `sei-rpc-node` container alongside the 4-validator cluster. Validators read AUTOBAHN/GIGA_EXECUTOR/GIGA_OCC from docker-compose, but `make run-rpc-node-skipbuild` only forwarded GIGA_STORAGE and RECEIPT_BACKEND — so under AUTOBAHN=true the rpc node came up in CometBFT mode, couldn't talk to the Autobahn validators, and the CometBFT RPC server never bound (state sync hung on connection refused). Forward the four missing vars (AUTOBAHN, GIGA_EXECUTOR, GIGA_OCC, CLUSTER_SIZE) in both run-rpc-node targets, and mirror the validator step4_config_override.sh logic in the rpc node's step1: generate autobahn.json with `seid tendermint gen-autobahn-config` against the shared build/generated/node_* dirs (mounted in), inject autobahn-config-file into config.toml, and apply giga_executor / occ_enabled to app.toml when requested. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Autobahn doesn't run the CometBFT state-sync reactor (gated by
!gigaEnabled in sei-tendermint/node/node.go) and its BlockStore stays
empty, so /status's SyncInfo.latest_block_height is always 0 (per the
existing comment in integration_test/autobahn/autobahn_test.go). The
dumb-enabled Autobahn Chain Operation matrix entry hung on the
rpc-node `seid status` readiness loop and would have failed
statesync_operation.yaml / verify_statesync_flatkv_digest.sh
afterwards regardless.
Keep the two parts that work without state sync:
- snapshot_operation.yaml: pure filesystem check on a validator
- verify_cross_validator_flatkv_digest.sh: compares FlatKV across
the 4 validators at a shared committed height; validators commit
blocks normally under Autobahn so this is meaningful.
Patch verify_cross_validator_flatkv_digest.sh's node_height() to read
last_block_height from /abci_info instead of `seid status` so it works
under both consensus modes.
Skip the rpc-node-side scripts until upstream Autobahn supports state
sync; re-add then.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Validators are committing blocks (FlatKV version=2787 in logs) but my /abci_info-based node_height() returned 0 for all 4 the entire 180s wait window. Add a one-shot diagnostic that prints the raw responses from /abci_info, /status, and `seid status` on sei-node-0 before entering the wait loop, so we can see whether: - /abci_info is unreachable / 404 / returns different schema - last_block_height is omitted (proto3 zero-value omitempty) - my jq path is wrong - or something else entirely Will be removed once node_height() is fixed. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Dumb-enable an
Autobahn Chain Operation Testmatrix entry that mirrors the existing CometBFTChain Operation Test, with the standard Autobahn env. Purpose: see which sub-step actually fails under Autobahn so we can decide what to keep, what to carve out, and what to wait on.Expected
statesync_operation.yamllikely fails — Autobahn doesn't drive CometBFT-style state sync todayNext step
Once CI tells us exactly what fails, follow-up PR can either:
Test plan
Autobahn Chain Operation TestChain Operation Teststays green