mirrors/tendermint
1
0
Fork 0
mirror of https://github.com/tendermint/tendermint.git synced 2026-01-08 14:21:14 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
0b8a62c87be84d002e252110d4974c57af4444c4
tendermint/test
History
William Banfield 0b8a62c87b abci: Synchronize FinalizeBlock with the updated specification (#7983) 
This change set implements the most recent version of `FinalizeBlock`. 

# What does this change actually contain?

* This change set is rather large but fear not! The majority of the files touched and changes are renaming `ResponseDeliverTx` to `ExecTxResult`. This should be a pretty inoffensive change since they're effectively the same type but with a different name.
* The `execBlockOnProxyApp` was totally removed since it served as just a wrapper around the logic that is now mostly encapsulated within `FinalizeBlock`
* The `updateState` helper function has been made a public method on `State`. It was being exposed as a shim through the testing infrastructure, so this seemed innocuous.
* Tests already existed to ensure that the application received the `ByzantineValidators` and the `ValidatorUpdates`, but one was fixed up to ensure that `LastCommitInfo` was being sent across.
* Tests were removed from the `psql` indexer that seemed to search for an event in the indexer that was not being created.

# Questions for reviewers
* We store this [ABCIResponses](5721a13ab1/proto/tendermint/state/types.pb.go (L37)) type in the data base as the block results. This type has changed since v0.35 to contain the `FinalizeBlock` response. I'm wondering if we need to do any shimming to keep the old data retrieveable?
* Similarly, this change is exposed via the RPC through [ResultBlockResults](5721a13ab1/rpc/coretypes/responses.go (L69)) changing. Should we somehow shim or notify for this change? 


closes: #7658
2022-03-04 22:32:37 +00:00
..
app
rpc: rework how responses are written back via HTTP (#7575)
2022-01-12 17:25:58 -08:00
docker
tests: update docker versions to match build version (#7646)
2022-01-20 12:17:32 -05:00
e2e
abci: Synchronize FinalizeBlock with the updated specification (#7983)
2022-03-04 22:32:37 +00:00
fuzz
node: nodes should fetch state on startup (#8062)
2022-03-04 12:23:57 -05:00
Makefile
build: declare packages variable in correct makefile (#7402)
2021-12-07 14:53:22 -05:00
README.md
abci: remove counter app (#6684)
2021-07-12 14:55:32 +00:00
test_cover.sh
ci: use cheaper codecov data collection (#7009)
2021-09-27 15:22:25 -04:00

README.md

Tendermint Tests

The unit tests (ie. the go test s) can be run with make test. The integration tests can be run with make test_integrations.

Running the integrations test will build a docker container with local version of tendermint and run the following tests in docker containers:

  • go tests, with --race
    • includes test coverage
  • app tests
    • kvstore app over socket
  • persistence tests
    • crash tendermint at each of many predefined points, restart, and ensure it syncs properly with the app

Fuzzing

Fuzzing of various system inputs.

See ./fuzz/README.md for more details.