Skip to content
.github/workflows/ci.yaml

feat: export policies #741

Sign in to view logs

feat: export policies

feat: export policies #741

Triggered via pull request November 10, 2024 14:55
@kopy-katkopy-kat
opened #159
feat/export-policies
Status Failure
Total duration 3m 26s
Artifacts –

ci.yaml

on: pull_request
lint  /  forge-lint
1m 1s
lint / forge-lint
build  /  forge-build
1m 20s
build / forge-build
test  /  forge-test
1m 36s
test / forge-test
test-simulate  /  forge-test
1m 50s
test-simulate / forge-test
test-multi-account  /  forge-test
1m 41s
test-multi-account / forge-test
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
test-simulate / forge-test
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
test-simulate / forge-test
The operation was canceled.
lint / forge-lint: src/deployment/RegistryDeployer.sol#L115
Error message for require is too long: 44 counted / 32 allowed
lint / forge-lint: src/deployment/RegistryDeployer.sol#L115
GC: Use Custom Errors instead of require statements
lint / forge-lint: src/deployment/RegistryDeployer.sol#L133
GC: Use Custom Errors instead of require statements
lint / forge-lint: src/deployment/RegistryDeployer.sol#L193
Avoid to use inline assembly. It is acceptable only in rare cases