-
Notifications
You must be signed in to change notification settings - Fork 131
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
Explore zombienet integration #2472
Comments
@bkontur is this similar to what you have implemented, right? |
partially, I use zombienet for local run, |
@serban300 to take a look. |
I researched this issue a bit. It seems that cumulus uses The problem is that |
Also opened a draft PR in zombienet that adds support for multiple networks in Might be missing some corner cases and might need some polishing, but overall adding support for multiple networks seems possible. |
Covered corner cases and polished the code. The zombienet PR for adding multiple networks support is ready for review: paritytech/zombienet#788 . Waiting on it. |
The zombienet team decided that it would be better to support this use case with a different cli tool that they will be working on. Some details here: paritytech/zombienet#796 (comment) We'll wait for the new tool |
ok, only one zombienet could totally simplify local run, but lets wait for a new tool, |
* [ci] improve cancel-pipeline job * fix trigger * fix trigger * add file to trigger * test job fail * fix trigger * fix indent * fix before_script * add comment * remove debuag fail from test-linux-stable
I'll try to play with zombienet tests here (in this repo). We may then (try to) migrate those tests to |
I'm gonna close it - we now have a basic test (unfortunately with a hacky test runner) in |
It looks cool what Adrian has introduced for BEEFY (paritytech/polkadot#5840). Would it make sense for us to make some zombienet tests?
Main directions are:
The text was updated successfully, but these errors were encountered: