Files

T

pezkuwichain 379cb741ed feat: Rebrand Polkadot/Substrate references to PezkuwiChain

This commit systematically rebrands various references from Parity Technologies'
Polkadot/Substrate ecosystem to PezkuwiChain within the kurdistan-sdk.

Key changes include:
- Updated external repository URLs (zombienet-sdk, parity-db, parity-scale-codec, wasm-instrument) to point to pezkuwichain forks.
- Modified internal documentation and code comments to reflect PezkuwiChain naming and structure.
- Replaced direct references to  with  or specific paths within the  for XCM, Pezkuwi, and other modules.
- Cleaned up deprecated  issue and PR references in various  and  files, particularly in  and  modules.
- Adjusted image and logo URLs in documentation to point to PezkuwiChain assets.
- Removed or rephrased comments related to external Polkadot/Substrate PRs and issues.

This is a significant step towards fully customizing the SDK for the PezkuwiChain ecosystem.

2025-12-14 00:04:10 +03:00

2.4 KiB

Raw Blame History

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

teyrchains At the moment this directory only have one test related to teyrchains: /teyrchains-smoke-test, that check the teyrchain 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 -> pezkuwi/target/testnet/adder-collator
malus -> pezkuwi/target/testnet/malus
pezkuwi -> pezkuwi/target/testnet/pezkuwi, pezkuwi/target/testnet/pezkuwi-prepare-worker, pezkuwi/target/testnet/pezkuwi-execute-worker
pezkuwi-collator -> pezcumulus/target/release/pezkuwi-teyrchain
undying-collator -> pezkuwi/target/testnet/undying-collator

To build them use:

adder-collator -> cargo build --profile testnet -p test-teyrchain-adder-collator
undying-collator -> cargo build --profile testnet -p test-teyrchain-undying-collator
malus -> cargo build --profile testnet -p pezkuwi-test-malus
pezkuwi (in the PezkuwiChain repo) and pezkuwi-collator (in Pezcumulus 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=(
  "~/pezkuwi/target/release"
  "~/pezkuwi/target/testnet"
  "~/pezcumulus/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-teyrchains-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.

2.4 KiB Raw Blame History