Skip to content

[ETCM-286] Adjustments to rpc tests #776

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

Merged
3 commits merged into from
Nov 9, 2020
Merged

[ETCM-286] Adjustments to rpc tests #776

3 commits merged into from
Nov 9, 2020

Conversation

mmrozek
Copy link
Contributor

@mmrozek mmrozek commented Nov 5, 2020

Description

Fix rpc tests

@mmrozek mmrozek requested review from kapke, KonradStaniec and a user November 5, 2020 12:44
@mirkoAlic
Copy link
Contributor

Maybe we could add this as part of the buildkite flow?

@@ -899,7 +899,7 @@ class RpcApiTests extends AnyFlatSpec with Matchers with Logger {
nonExistingFilterChanges.getLogs.asScala.size shouldEqual 0
}

it should "eth_newBlockFilter" taggedAs (PrivNet, MainNet) in new ScenarioSetup {
it should "eth_newBlockFilter" taggedAs (PrivNet) in new ScenarioSetup {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i'm curious, why MainNet is not needed anymore?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The test is flaky when used in such a big network as mainnet. I am not sure if it is because of reorgs, too big response or sth else. Testing PrivNet tests the required behaviour so it should be enough

Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ghost ghost merged commit 2063f79 into develop Nov 9, 2020
@ghost ghost deleted the ETCM-286-fix-rpc-tests branch November 9, 2020 06:53
kapke pushed a commit that referenced this pull request Nov 16, 2020
This pull request was closed.
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 this pull request may close these issues.

3 participants