Skip to content
.github/workflows/ci.yaml

feat(ModuleKitHelpers): add verifyModuleStorageWasCleared #732

Sign in to view logs

feat(ModuleKitHelpers): add verifyModuleStorageWasCleared

feat(ModuleKitHelpers): add verifyModuleStorageWasCleared #732

Triggered via pull request November 4, 2024 03:52
@highskorehighskore
synchronize #155
feat/unistall-storage-check
Status Failure
Total duration 3m 36s
Artifacts –

ci.yaml

on: pull_request
lint  /  forge-lint
1m 5s
lint / forge-lint
build  /  forge-build
1m 24s
build / forge-build
test  /  forge-test
1m 24s
test / forge-test
test-simulate  /  forge-test
1m 52s
test-simulate / forge-test
test-multi-account  /  forge-test
1m 32s
test-multi-account / forge-test
Fit to window
Zoom out
Zoom in

Annotations

1 error and 4 warnings
test-simulate / forge-test
Process completed with exit code 1.
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