Skip to content

implement seconds per liquidity type and update storage structs funct… #1111

implement seconds per liquidity type and update storage structs funct…

implement seconds per liquidity type and update storage structs funct… #1111

Triggered via pull request August 29, 2024 12:29
Status Failure
Total duration 29m 6s
Artifacts

tests.yml

on: pull_request
Uint and e2e tests
28m 55s
Uint and e2e tests
Release build the contract + lint
25m 12s
Release build the contract + lint
Build and test SDK
25m 27s
Build and test SDK
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 14 warnings
Release build the contract + lint
Process completed with exit code 127.
Release build the contract + lint
failed to run custom build command for `contracts-parachain-runtime v0.39.0`
Release build the contract + lint
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
Build and test SDK
failed to run custom build command for `contracts-parachain-runtime v0.39.0`
Build and test SDK
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
Build and test SDK
Process completed with exit code 127.
Uint and e2e tests
Process completed with exit code 127.
Uint and e2e tests
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
Release build the contract + lint
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Release build the contract + lint
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Release build the contract + lint
package `bytemuck v1.14.3` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
Release build the contract + lint
[email protected]: Could not find `Cargo.lock` for `/home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/contracts-parachain-runtime-0.39.0/Cargo.toml`, while searching from `/tmp/cargo-installtlhyco/release/build/contracts-parachain-runtime-61b3d5e8d6a644cd/out`. To fix this, point the `WASM_BUILD_WORKSPACE_HINT` env variable to the directory of the workspace being compiled.
Release build the contract + lint
build failed, waiting for other jobs to finish...
Build and test SDK
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build and test SDK
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build and test SDK
package `bytemuck v1.14.3` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
Build and test SDK
[email protected]: Could not find `Cargo.lock` for `/home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/contracts-parachain-runtime-0.39.0/Cargo.toml`, while searching from `/tmp/cargo-installBQ8wwP/release/build/contracts-parachain-runtime-61b3d5e8d6a644cd/out`. To fix this, point the `WASM_BUILD_WORKSPACE_HINT` env variable to the directory of the workspace being compiled.
Build and test SDK
build failed, waiting for other jobs to finish...
Uint and e2e tests
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Uint and e2e tests
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Uint and e2e tests
package `ahash v0.7.6` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
Uint and e2e tests
package `elliptic-curve v0.13.5` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked