Skip to content

[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
wants to merge 312 commits into
base: master
Choose a base branch
from

Conversation

lrubasze
Copy link
Contributor

This is a test PR

@lrubasze lrubasze requested review from a team and koute as code owners June 25, 2025 09:07
@cla-bot-2021
Copy link

cla-bot-2021 bot commented Jun 25, 2025

User @Stephenlawrence00, please sign the CLA here.

Base automatically changed from ci/make-zombienet-ci-great-again to master June 26, 2025 10:59
lrubasze and others added 14 commits June 26, 2025 13:55
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]>
…-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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants