mirror of https://github.com/pezkuwichain/pezkuwi-subxt.git synced 2026-04-26 16:57:58 +00:00

Files

T

James Wilson 4ca50ef844 Add nightly CI check against latest substrate. (#335 )

* Add nightly check and use specific version (currently the same) in PR checks

* wrong var name, whoops

* Create GH issue if nightly run fails

* need tokio feature for RpcClient; match dependency in root Cargo.toml.

* Ensure substrate command is properly cleaned up in the event of a panic, to prevent blocking

* increase retry limit again

* fmt

* Tweak text for nightly-run-failed issue template

* Run nightly-CI every 5mins for testing

* I clearly dont use cron enough

* Put back cron timings to 8am daily

* break a test

* revert nightly workflow again (doesnt run off master) and testing rust workflow

* more testing..

* undo testing things; seems to work

* tidy up; substrate url at top of both CI files

2021-11-30 15:01:25 +00:00

src

Ensure metadata is in sync with running node during tests (#333 )

2021-11-29 09:39:40 +00:00

build.rs

Add nightly CI check against latest substrate. (#335 )

2021-11-30 15:01:25 +00:00

Cargo.toml

Add nightly CI check against latest substrate. (#335 )

2021-11-30 15:01:25 +00:00

README.md

Ensure metadata is in sync with running node during tests (#333 )

2021-11-29 09:39:40 +00:00

README.md

test-runtime

The logic for this crate exists mainly in the build.rs file.

At compile time, this crate will:

Spin up a local substrate binary (set the SUBSTRATE_NODE_PATH env var to point to a custom binary, otehrwise it'll look for substrate on your PATH).
Obtain metadata from this node.
Export the metadata and a node_runtime module which has been annotated using the subxt proc macro and is based off the above metadata.

The reason for doing this is that our integration tests (which also spin up a Substrate node) can then use the generated subxt types from the exact node being tested against, so that we don't have to worry about metadata getting out of sync with the binary under test.