-
Notifications
You must be signed in to change notification settings - Fork 696
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
zombienet-bridges-*
test failures
#6161
Comments
I think it should be related to the: #6133 |
The error in the linked failure is not related to this:
That might also be a problem, but I think we will stumble upon it later, after fixing the first one |
I updated the |
Thanks ! This will probably fix the error above. Anyway, I see that other runs fail with:
So setting up the bridge times out. This is probably related to something else. Looking into it. |
This is where it started failing: #6039 The problem is that the process of setting up the bridge is unsuccessful. For example for the Rococo side it fails here:
I don't think the nodejs heap size is the issue here. Checking. |
Yes, I try increasing the size of the heap (2x) and I get the same error, something is leaking and consuming memory. I also check with Tarik about recent changes in Thanks! |
Now the Rococo -> Westend transfer works. The Westend -> Rococo transfer fails: Doesn't seem related to the signed extensions. Investigating |
Looks like the issue was introduced by #5461 Investigating why |
Closes #6161 Westend BridgeHub freezes for a while at block 3 and if we try to init the bridge and fund the accounts during that time, it fails. So we wait untill all the parachains produced at least 10 blocks, in order to make sure that they work reliably.
Closes paritytech#6161 Westend BridgeHub freezes for a while at block 3 and if we try to init the bridge and fund the accounts during that time, it fails. So we wait untill all the parachains produced at least 10 blocks, in order to make sure that they work reliably.
Closes paritytech#6161 Westend BridgeHub freezes for a while at block 3 and if we try to init the bridge and fund the accounts during that time, it fails. So we wait untill all the parachains produced at least 10 blocks, in order to make sure that they work reliably.
Closes paritytech#6161 Westend BridgeHub freezes for a while at block 3 and if we try to init the bridge and fund the accounts during that time, it fails. So we wait untill all the parachains produced at least 10 blocks, in order to make sure that they work reliably.
Closes paritytech#6161 Westend BridgeHub freezes for a while at block 3 and if we try to init the bridge and fund the accounts during that time, it fails. So we wait untill all the parachains produced at least 10 blocks, in order to make sure that they work reliably.
Closes paritytech#6161 Westend BridgeHub freezes for a while at block 3 and if we try to init the bridge and fund the accounts during that time, it fails. So we wait untill all the parachains produced at least 10 blocks, in order to make sure that they work reliably.
Closes paritytech#6161 Westend BridgeHub freezes for a while at block 3 and if we try to init the bridge and fund the accounts during that time, it fails. So we wait untill all the parachains produced at least 10 blocks, in order to make sure that they work reliably.
Closes paritytech#6161 Westend BridgeHub freezes for a while at block 3 and if we try to init the bridge and fund the accounts during that time, it fails. So we wait untill all the parachains produced at least 10 blocks, in order to make sure that they work reliably.
Reported in #6161 (comment) Fixes a bug introduced in #5461, where the claim queue would contain entries even if the validator groups storage is empty (which happens during the first session). This PR sets the claim queue core count to be the minimum between the num_cores param and the number of validator groups TODO: - [x] prdoc - [x] unit test
The bridge zombienet tests are failing.
For example:
https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/7607843
https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/7609603
We need to investigate this.
The text was updated successfully, but these errors were encountered: