-
Notifications
You must be signed in to change notification settings - Fork 224
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
RPC integration tests failing on CI #304
Comments
Related comment: #120 (comment) I'll have a look. |
Yes we should target v0.34 but we need some lead time so our tests shouldn't fail just because we're behind the latest breaking release. We should make sure the tests run against something stable ... |
Closes informalsystems#304 Also rename test-integration-ignored to test-integration-latest. The latest integration tracks whether we're maintaining parity with the latest development version of tendermint-go, while the stable integration ensures we avoid regressions.
Closes informalsystems#304 Also renames test-integration-ignored to test-integration-latest. With this change, CI runs two integration tests: 1. A `stable` test to protect against regressions, run against a pinned version of the tendermint/tendermint docker image. 2. A `latest` test to track whether we're maintaining parity with the latest development version of tendermint-go. Signed-off-by: Shon Feder <[email protected]>
Closes informalsystems#304 Also renames test-integration-ignored to test-integration-latest. With this change, CI runs two integration tests: 1. A `stable` test to protect against regressions, run against a pinned version of the tendermint/tendermint docker image. 2. A `latest` test to track whether we're maintaining parity with the latest development version of tendermint-go. Signed-off-by: Shon Feder <[email protected]>
Closes informalsystems#304 Also renames test-integration-ignored to test-integration-latest. With this change, CI runs two integration tests: 1. A `stable` test to protect against regressions, run against a pinned version of the tendermint/tendermint docker image. 2. A `latest` test to track whether we're maintaining parity with the latest development version of tendermint-go. Signed-off-by: Shon Feder <[email protected]>
* Add integration test pinned to tendermint-go v0.33 Closes #304 Also renames test-integration-ignored to test-integration-latest. With this change, CI runs two integration tests: 1. A `stable` test to protect against regressions, run against a pinned version of the tendermint/tendermint docker image. 2. A `latest` test to track whether we're maintaining parity with the latest development version of tendermint-go. Signed-off-by: Shon Feder <[email protected]> * Remove test for hardcoded ABCI version Hardcoding a test for the version in this way makes it impossible to run the integration tests against different ABCI versions. This change proposes one solution to address this problem and to the underlying issue behind, e.g., - #249 - #238 - #233 My sense is that, if we want to set a strict abci version requirement for the rpc client, then we should put that in the source code itself. E.g., we might put a check on the client that ensures the abci version is within a specified version range known to be supported. If the version is outside that range, we could either error out or log errors/warning to alert users that we don't guarantee compatibility. However, the current approach of hardcoding in a version in the integration test seems to create a lot of busy work due to uninformative test failures and it's not obvious what value it delivers. If the integration tests are meant to test that the RPC client integrates correctly with ACBI, should we really consider integration to have failed when everything works as expected while interfacing with an older (or newer) version? Signed-off-by: Shon Feder <[email protected]> * Update changelog Signed-off-by: Shon Feder <[email protected]>
They are still failing now (because tests against latest are still running and marked as required): https://github.com/informalsystems/tendermint-rs/runs/772419078#step:5:271 |
Closes informalsystems#304 Signed-off-by: Shon Feder <[email protected]>
Closes informalsystems#304 We want to run the integration test against the latest version, but don't want it to clutter CI with failures. Tests against the pinned stable version still fail. Also fixes some whitespace. Signed-off-by: Shon Feder <[email protected]>
Closes informalsystems#304 We want to run the integration test against the latest version, but don't want it to clutter CI with failures. Tests against the pinned stable version still fail. Also fixes some whitespace. Signed-off-by: Shon Feder <[email protected]>
Closes informalsystems#304 We want to run the integration test against the latest version, but don't want it to clutter CI with failures. Tests against the pinned stable version still fail. Also fixes some whitespace. Signed-off-by: Shon Feder <[email protected]>
* Set integration-test-latest to continue_on_error Closes #304 We want to run the integration test against the latest version, but don't want it to clutter CI with failures. Tests against the pinned stable version still fail. Also fixes some whitespace. Signed-off-by: Shon Feder <[email protected]> * Update changelog Also fixed previous entries, so they pointed to their originating issue rather than the PR that implemented them, to be consistent with other entries. * fixup! Set integration-test-latest to continue_on_error
The RPC integration tests are currently failing on CI.
Affected PRs are:
Here's an excerpt from the build logs for #302:
Click to show log
The text was updated successfully, but these errors were encountered: