-
Notifications
You must be signed in to change notification settings - Fork 710
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
Fix flaky zombienet test zombienet-polkadot-smoke-0004-coretime-smoke-test
#6226
Closed
Tracked by
#5852
Labels
T10-tests
This PR/Issue is related to tests.
Comments
pepoviola
added a commit
that referenced
this issue
Oct 24, 2024
Artefacts are starting to get removed so I persisted the ones from:
In both cases the problem seems to be:
I'm checking further why no cores are assigned to the para. |
Thanks @tdimitrov! |
github-merge-queue bot
pushed a commit
that referenced
this issue
Oct 28, 2024
In the test log I noticed that the batch transaction which configures the coretime chain fails. However when rerunning the transaction manually - it worked. Then I noticed that the coretime chain is initially registered via zombienet and then re-registered via `0004-configure-relay.js`. Because of this there is a period of time when it's not producing blocks and `0004-configure-broker.js` fails to setup the coretime chain. My theory is that the transaction has failed because the coretime chain is stalled during the re-registration. Fixes #6226
Awesome! Thanks @tdimitrov 🙌 |
xermicus
pushed a commit
that referenced
this issue
Oct 28, 2024
In the test log I noticed that the batch transaction which configures the coretime chain fails. However when rerunning the transaction manually - it worked. Then I noticed that the coretime chain is initially registered via zombienet and then re-registered via `0004-configure-relay.js`. Because of this there is a period of time when it's not producing blocks and `0004-configure-broker.js` fails to setup the coretime chain. My theory is that the transaction has failed because the coretime chain is stalled during the re-registration. Fixes #6226
mordamax
pushed a commit
to paritytech-stg/polkadot-sdk
that referenced
this issue
Oct 29, 2024
In the test log I noticed that the batch transaction which configures the coretime chain fails. However when rerunning the transaction manually - it worked. Then I noticed that the coretime chain is initially registered via zombienet and then re-registered via `0004-configure-relay.js`. Because of this there is a period of time when it's not producing blocks and `0004-configure-broker.js` fails to setup the coretime chain. My theory is that the transaction has failed because the coretime chain is stalled during the re-registration. Fixes paritytech#6226
mordamax
pushed a commit
to paritytech-stg/polkadot-sdk
that referenced
this issue
Oct 29, 2024
In the test log I noticed that the batch transaction which configures the coretime chain fails. However when rerunning the transaction manually - it worked. Then I noticed that the coretime chain is initially registered via zombienet and then re-registered via `0004-configure-relay.js`. Because of this there is a period of time when it's not producing blocks and `0004-configure-broker.js` fails to setup the coretime chain. My theory is that the transaction has failed because the coretime chain is stalled during the re-registration. Fixes paritytech#6226
github-merge-queue bot
pushed a commit
that referenced
this issue
Oct 30, 2024
polkadot/zombienet_tests/smoke/0004-coretime-smoke-test.zndsl still timeouts on CI from time to time. Bumping the timeout a bit more. Related to #6226 --------- Signed-off-by: Oliver Tale-Yazdi <[email protected]> Co-authored-by: GitHub Action <[email protected]> Co-authored-by: Oliver Tale-Yazdi <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some examples from yesterday ( 32 of 57 fails)
https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/7628951
https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/7628817
https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/7628682
https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/7628615
https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/7628483
https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/7628416
https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/7628285
https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/7628229
https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/7627210
https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/7627074
https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/7626873
https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/7626039
https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/7625972
https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/7625769
https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/7625639
https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/7625576
https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/7625564
https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/7624714
https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/7624291
https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/7624224
https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/7623747
https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/7623613
https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/7623345
https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/7623211
cc @paritytech/parachains-core
The text was updated successfully, but these errors were encountered: