Remove storage read #4017

Triggered via pull request October 22, 2024 12:33

acerone85

synchronize #847

681_remove_storage_read

Status Failure

Total duration 15m 23s

Artifacts –

ci.yml

on: pull_request

publish-wasm-packages-check

4m 10s

Matrix: cargo

verifications-complete

Publish code coverage report on GitHub pages branch

publish

publish_wasm_packages

Annotations

11 errors and 63 warnings

publish-check

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

publish-check

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

publish-check

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

publish-check

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

publish-check

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

publish-check

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

publish-check

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

publish-check

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

publish-check

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

cargo (clippy, --all-targets --all-features -- -D warnings -D clippy::dbg_macro)

Process completed with exit code 101.

cargo (check, --target wasm32-unknown-unknown -p fuel-crypto --no-default-features)

The self-hosted runner: buildjet.com_6a6ee15a-7150-4fb3-beaa-80f21a8ac5f1 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

publish-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-check

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, 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-toml-fmt-check

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

cargo-toml-fmt-check

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2. 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 use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, rustsec/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

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/