mirror of https://github.com/pezkuwichain/pezkuwi-subxt.git synced 2026-05-31 02:51:01 +00:00

Files

T

Andrei Sandu 13ca339e4a Adjust zombienet test resources and logic (#4032 )

One more try to make this test robust from a resource perspective.

---------

Signed-off-by: Andrei Sandu <andrei-mihail@parity.io>
Co-authored-by: Javier Viola <javier@parity.io>

2024-04-12 10:08:34 +00:00

elastic_scaling

Adjust zombienet test resources and logic (#4032 )

2024-04-12 10:08:34 +00:00

functional

Elastic scaling: add e2e test (#3929 )

2024-04-05 09:06:43 +00:00

misc

Remove AssignmentProviderConfig and use parameters from HostConfiguration instead (#3181 )

2024-02-29 07:12:02 +00:00

smoke

Enable async backing on all testnet system chains (#2949 )

2024-02-02 13:58:21 +00:00

.set_env

Make zombienet tests native friendly (#6588 )

2023-01-28 12:00:45 +00:00

README.md

Markdown linter (#1309 )

2023-09-04 12:02:32 +03:00

README.md

Zombienet tests

The content of this directory is meant to be used by Parity's private CI/CD infrastructure with private tools. At the moment those tools are still early stage of development and we don't know if / when they will available for public use.

Contents of this directory

parachains At the moment this directory only have one test related to parachains: /parachains-smoke-test, that check the parachain registration and the block height.

Resources

Running tests locally

To run any test locally use the native provider (zombienet test -p native ...) you need first build the binaries. They are:

adder-collator -> polkadot/target/testnet/adder-collator
malus -> polkadot/target/testnet/malus
polkadot -> polkadot/target/testnet/polkadot, polkadot/target/testnet/polkadot-prepare-worker, polkadot/target/testnet/polkadot-execute-worker
polkadot-collator -> cumulus/target/release/polkadot-parachain
undying-collator -> polkadot/target/testnet/undying-collator

To build them use:

adder-collator -> cargo build --profile testnet -p test-parachain-adder-collator
undying-collator -> cargo build --profile testnet -p test-parachain-undying-collator
malus -> cargo build --profile testnet -p polkadot-test-malus
polkadot (in the Polkadot repo) and polkadot-collator (in Cumulus repo) -> cargo build --profile testnet

One solution is to use the .set_env file (from this directory) and fill the CUSTOM_PATHS before source it to patch the PATH of your system to find the binaries you just built.

E.g.:

$ cat .set_env
(...)
# by the order of this array
CUSTOM_PATHS=(
  "~/polkadot/target/release"
  "~/polkadot/target/testnet"
  "~/cumulus/target/release"
)
(...)

source .set_env

Then you have your PATH customized and ready to run zombienet. NOTE: You should need to do this ones per terminal session, since we are patching the PATH and re-exporting. Or you can also source this file in your .bashrc file to get executed automatically in each new session.

Example:

You can run a test locally by executing:

zombienet test -p native 0001-parachains-pvf.zndsl

Questions / permissions

Ping in element Javier (@javier:matrix.parity.io) to ask questions or grant permission to run the test from your local setup.