CI

chore: use sdk v0.54.0 to enable forc-client deployments to beta5 #17304

Sign in to view logs

Triggered via pull request January 7, 2024 16:45

kayagokalp

synchronize #5433

kayagokalp/wallet-bump-to-0.4.1

Status Failure

Total duration 19m 6s

Artifacts –

ci.yml

on: pull_request

build-sway-lib-core

build-sway-lib-std

build-sway-examples

build-forc-test-project

cargo-build-workspace

cargo-fmt-check

cargo-run-e2e-test

cargo-run-e2e-test-evm

cargo-test-lib-std

cargo-test-workspace

cargo-unused-deps-check

pre-publish-check

build-reference-examples

forc-fmt-check-sway-lib-core

forc-fmt-check-sway-lib-std

forc-fmt-check-sway-examples

forc-fmt-check-panic

build-forc-doc-sway-lib-std

cargo-toml-fmt-check

cargo-run-e2e-test-midenvm

forc-run-benchmarks

forc-unit-tests

forc-pkg-fuels-deps-check

notify-slack-on-failure

build-publish-master-image

build-publish-release-image

Matrix: Build and upload forc binaries to release

Annotations

1 error and 1 warning

cargo-run-e2e-test

Process completed with exit code 1.

cargo-toml-fmt-check

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