L1 contracts CI

chore(l1-contracts): Migrate L1 Contracts to Custom Errors #1716

Sign in to view logs

Triggered via pull request May 16, 2024 23:35

koloz193

opened #477

zk-l1-custom-errors

Status Failure

Total duration 5m 27s

Artifacts –

l1-contracts-ci.yaml

on: pull_request

check-verifier-generator

Annotations

10 errors and 8 warnings

lint: l1-contracts/contracts/state-transition/chain-deps/DiamondInit.sol#L21

GC: Use Custom Errors instead of require statements

lint: l1-contracts/contracts/state-transition/chain-deps/DiamondInit.sol#L22

GC: Use Custom Errors instead of require statements

lint: l1-contracts/contracts/state-transition/chain-deps/DiamondInit.sol#L23

GC: Use Custom Errors instead of require statements

lint: l1-contracts/contracts/state-transition/chain-deps/DiamondInit.sol#L24

GC: Use Custom Errors instead of require statements

lint: l1-contracts/contracts/state-transition/chain-deps/DiamondInit.sol#L25

GC: Use Custom Errors instead of require statements

lint: l1-contracts/contracts/state-transition/chain-deps/DiamondInit.sol#L26

GC: Use Custom Errors instead of require statements

lint: l1-contracts/contracts/state-transition/chain-deps/DiamondInit.sol#L27

GC: Use Custom Errors instead of require statements

lint: l1-contracts/contracts/state-transition/chain-deps/DiamondInit.sol#L28

GC: Use Custom Errors instead of require statements

lint: l1-contracts/contracts/state-transition/chain-deps/DiamondInit.sol#L29

GC: Use Custom Errors instead of require statements

lint: l1-contracts/contracts/state-transition/chain-deps/DiamondProxy.sol#L14

GC: Use Custom Errors instead of require statements

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@v3, actions/cache/save@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

check-verifier-generator

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions-rs/toolchain@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

check-verifier-generator

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

check-verifier-generator

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

check-verifier-generator

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

check-verifier-generator

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

check-verifier-generator

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/