Back to pull request #2429

Replace task `run()` return result with custom enum #10782

Sign in to view logs

Re-run triggered November 19, 2024 13:27

AurelienFT

#2429

chore/introduce-task-result-enum

Status Success

Total duration 13m 27s

Artifacts –

ci.yml

on: pull_request

Check Changelog

verify-tag-version

lint-toml-files

prevent-openssl

publish-crates-check

Matrix: cargo-verifications

verifications-complete

Matrix: Release fuel-core binaries

Annotations

13 errors and 32 warnings

publish-crates-check

Unable to determine latest modification time for local package 'fuel-core' due to: 'TypeError: Cannot read properties of null (reading 'target')'

publish-crates-check

Unable to determine latest modification time for local package 'fuel-core-wasm-executor' due to: 'TypeError: Cannot read properties of null (reading 'target')'

publish-crates-check

Unable to determine latest modification time for local package 'fuel-core-compression' due to: 'TypeError: Cannot read properties of null (reading 'target')'

publish-crates-check

Unable to determine latest modification time for local package 'fuel-gas-price-algorithm' due to: 'TypeError: Cannot read properties of null (reading 'target')'

publish-crates-check

Unable to determine latest modification time for local package 'fuel-core-gas-price-service' due to: 'TypeError: Cannot read properties of null (reading 'target')'

publish-crates-check

Unable to determine latest modification time for local package 'fuel-core-keygen-bin' due to: 'TypeError: Cannot read properties of null (reading 'target')'

publish-crates-check

Unable to determine latest modification time for local package 'fuel-core-keygen' due to: 'TypeError: Cannot read properties of null (reading 'target')'

publish-crates-check

Unable to determine latest modification time for local package 'fuel-core-consensus-module' due to: 'TypeError: Cannot read properties of null (reading 'target')'

publish-crates-check

Unable to determine latest modification time for local package 'fuel-core-types' due to: 'TypeError: Cannot read properties of null (reading 'target')'

publish-crates-check

Unable to determine latest modification time for local package 'fuel-core-chain-config' due to: 'TypeError: Cannot read properties of null (reading 'target')'

cargo-verifications (nextest, run --all-features --workspace)

The process '/home/runner/.cargo/bin/cargo' failed with exit code 101

cargo-verifications (nextest, run -p fuel-core --lib executor --features wasm-executor, FUEL_ALWA...

The process '/home/runner/.cargo/bin/cargo' failed with exit code 101

cargo-verifications (nextest, run -p fuel-core --no-default-features)

The process '/home/runner/.cargo/bin/cargo' failed with exit code 101

Check Changelog

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

publish-crates-check

The following actions uses node12 which is deprecated and will be forced to run on node16: FuelLabs/publish-crates@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

publish-crates-check

The following actions use a deprecated Node.js version and will be forced to run on node20: FuelLabs/publish-crates@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

cargo-audit

The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/audit-check@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

cargo-audit

The following actions use a deprecated Node.js version and will be forced to run on node20: actions-rs/audit-check@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

cargo-audit

6 warnings found!

cargo-audit

Unknown warning kind unsound found, please, file a bug

cargo-test-kms

The following actions use a deprecated Node.js version and will be forced to run on node20: buildjet/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

cargo-verifications (clippy, --all-targets --all-features)

The following actions use a deprecated Node.js version and will be forced to run on node20: buildjet/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

cargo-verifications (check, --all-targets)

The following actions use a deprecated Node.js version and will be forced to run on node20: buildjet/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

cargo-verifications (make, check --locked)

The following actions use a deprecated Node.js version and will be forced to run on node20: buildjet/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

cargo-verifications (doc, --all-features --workspace --no-deps)

The following actions use a deprecated Node.js version and will be forced to run on node20: buildjet/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

cargo-verifications (clippy, -p fuel-core-wasm-executor --target wasm32-unknown-unknown --no-defa...

The following actions use a deprecated Node.js version and will be forced to run on node20: buildjet/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

cargo-verifications (nextest, run --all-features --workspace)

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/

cargo-verifications (nextest, run -p fuel-core --lib executor --features wasm-executor, FUEL_ALWA...

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/

cargo-verifications (nextest, run --all-features --workspace)

The following actions use a deprecated Node.js version and will be forced to run on node20: buildjet/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/

cargo-verifications (nextest, run -p fuel-core --lib executor --features wasm-executor, FUEL_ALWA...

The following actions use a deprecated Node.js version and will be forced to run on node20: buildjet/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/

cargo-verifications (check, --manifest-path version-compatibility/Cargo.toml --workspace && cargo...

The following actions use a deprecated Node.js version and will be forced to run on node20: buildjet/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

cargo-verifications (nextest, run -p fuel-core-chain-config --no-default-features)

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/

cargo-verifications (nextest, run -p fuel-core-chain-config --no-default-features)

The following actions use a deprecated Node.js version and will be forced to run on node20: buildjet/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/

cargo-verifications (check, -p fuel-core-types --target wasm32-unknown-unknown --no-default-featu...

The following actions use a deprecated Node.js version and will be forced to run on node20: buildjet/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

cargo-verifications (build, -p fuel-core-bin --no-default-features --features production)

The following actions use a deprecated Node.js version and will be forced to run on node20: buildjet/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

cargo-verifications (nextest, run -p fuel-core --no-default-features)

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/

cargo-verifications (nextest, run -p fuel-core --no-default-features)

The following actions use a deprecated Node.js version and will be forced to run on node20: buildjet/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/

cargo-verifications (nextest, run -p fuel-core-client --no-default-features)

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/

cargo-verifications (nextest, run -p fuel-core-client --no-default-features)

The following actions use a deprecated Node.js version and will be forced to run on node20: buildjet/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/

cargo-verifications (check, -p fuel-core-client --target wasm32-unknown-unknown --no-default-feat...

The following actions use a deprecated Node.js version and will be forced to run on node20: buildjet/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

cargo-verifications (check, -p fuel-core-chain-config --target wasm32-unknown-unknown --no-defaul...

The following actions use a deprecated Node.js version and will be forced to run on node20: buildjet/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

cargo-verifications (check, -p fuel-core-executor --target wasm32-unknown-unknown --no-default-fe...

The following actions use a deprecated Node.js version and will be forced to run on node20: buildjet/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

cargo-verifications (check, -p fuel-core-storage --target wasm32-unknown-unknown --no-default-fea...

The following actions use a deprecated Node.js version and will be forced to run on node20: buildjet/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

cargo-verifications (nextest, run --workspace)

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/

cargo-verifications (nextest, run --workspace)

The following actions use a deprecated Node.js version and will be forced to run on node20: buildjet/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/