Skip to content
Solidity

MezoAllocator Withdrawals Improvements #1166

Sign in to view logs

MezoAllocator Withdrawals Improvements

MezoAllocator Withdrawals Improvements #1166

Triggered via pull request September 3, 2024 09:24
@nkubankuba
synchronize #717
mezo-allocator-withdraw-improvements
Status Failure
Total duration 1m 59s
Artifacts 1

solidity.yaml

on: pull_request
solidity-build  /  build-solidity
33s
solidity-build / build-solidity
solidity-deploy-dry-run
40s
solidity-deploy-dry-run
solidity-format
46s
solidity-format
solidity-slither
48s
solidity-slither
solidity-test
33s
solidity-test
solidity-integration-test
1m 7s
solidity-integration-test
solidity-deploy-testnet
0s
solidity-deploy-testnet
Fit to window
Zoom out
Zoom in

Annotations

1 error and 5 warnings
solidity-integration-test
Process completed with exit code 1.
solidity-slither
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
solidity-format: solidity/deploy/02_deploy_mezo_allocator.ts#L14
Unexpected console statement
solidity-format
Function name must be in mixedCase
solidity-format
Function order is incorrect, public view function can not go after internal function (line 36)
solidity-format
Function order is incorrect, external function can not go after public function (line 304)

Artifacts

Produced during runtime
Name Size
solidity-build Expired
2.02 MB