Skip to content
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.

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

never set "Node.ABCIProtocol" on e2e test #9894

Closed
tnasu opened this issue Dec 16, 2022 · 1 comment · Fixed by #9896
Closed

never set "Node.ABCIProtocol" on e2e test #9894

tnasu opened this issue Dec 16, 2022 · 1 comment · Fixed by #9896

Comments

@tnasu
Copy link

tnasu commented Dec 16, 2022

Tendermint version (use tendermint version or git rev-parse --verify HEAD if installed from source):

1a5d5ed

ABCI app (name for built-in, URL for self-written if it's publicly available):

(none)

Environment:

  • OS (e.g. from /etc/os-release):
  • Install tools:
  • Others:

(all)

What happened:

abci_protocol for each node is not set correctly. All are builtin.

ci.toml seems to set abci_protocol for each node:

But, LoadTestnet never loads/sets into ABCIProtocol since it depends on Testnet.ABCIProtocol and ci.toml doesn't define abci_protocol in the section of testnet:

What you expected to happen:

If abci_protocol should be set for each node, LoadTestnet function should modify.

Have you tried the latest version: yes/no

yes

How to reproduce it (as minimally and precisely as possible):

git clone git@github.com:tendermint/tendermint.git
cd tendermint/test/e2e
make runner
./build/runner -f ./networks/ci.toml setup

Logs (paste a small part showing an error (< 10 lines) or link a pastebin, gist, etc. containing more of the log file):

# cat ./networks/ci/validator02/config/app.toml
chain_id = "ci"
check_tx_delay = "0s"
dir = "data/app"
key_type = "ed25519"
mode = "validator"
persist_interval = 0
prepare_proposal_delay = "100ms"
privval_key = "config/priv_validator_key.json"
privval_server = "tcp://0.0.0.0:27559"
privval_state = "data/priv_validator_state.json"
process_proposal_delay = "100ms"
protocol = "builtin"
proxy_port = 5707
retain_blocks = 0
snapshot_interval = 0
sync_app = false

Config (you can paste only the changes you've made):

node command runtime flags:

Please provide the output from the http://<ip>:<port>/dump_consensus_state RPC endpoint for consensus bugs

Anything else we need to know:

@thanethomson
Copy link
Contributor

This was changed in #7078, but it doesn't look like the corresponding changes in the ci.toml file were made. We'll fix the ci.toml file accordingly, thanks for bringing it up!

In essence, how often will a single app chain be running nodes using different ABCI protocols on the same network? In our estimation, it's very unlikely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants