-
Notifications
You must be signed in to change notification settings - Fork 972
[DNM] Debug zombienet substrate tests #8968
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
Open
lrubasze
wants to merge
312
commits into
master
Choose a base branch
from
debug-zombienet-substrate-tests
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
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
This reverts commit a3b07d4.
…-audience node_dev'
…-sync-test-2' into debug-zombienet-substrate-tests
User @Stephenlawrence00, please sign the CLA here. |
closes #8985 I examined the two highlighted failures in the issue. In two cases, node _three_ fails to recover the required blocks. In the first case, the node is able to recover 16 blocks before encountering: ``` 2025-06-24 06:00:12.022 ERROR ⋮cumulus-relay-chain-streams: [Parachain] Failed to fetch pending candidates. error=JsonRpcError(Call(ErrorObject { code: ServerError(-32000), message: "Error when retrieving the call proof: Call proof query errors:\n- ConnectionShutdown", data: None })) 2025-06-24 06:00:12.023 ERROR ⋮cumulus-relay-chain-streams: [Parachain] Failed to fetch session index. error=JsonRpcError(Call(ErrorObject { code: ServerError(-32000), message: "Error when retrieving the call proof: No node available for call proof query", data: None })) ``` For the other failure we also see the same RPC-related error. Since for node three, the RPC is the internal light client, I just disabled it and purged it from this test. We will probably remove support for this experimental feature at some point, but currently does not have high priority. And should for sure not impact the stability of this test. --------- Co-authored-by: Lukasz Rubaszewski <[email protected]>
…mbienet-substrate-tests
…-warp-sync and 0003-block-building-warp-sync
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
R0-no-crate-publish-required
The change does not require any crates to be re-published.
T10-tests
This PR/Issue is related to tests.
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.
This is a test PR