Skip to content
Testing and coverage

feat: allow (de)activation of the wasm connection with an access control command #7357

Sign in to view logs

feat: allow (de)activation of the wasm connection with an access control command

feat: allow (de)activation of the wasm connection with an access control command #7357

Triggered via pull request July 25, 2024 23:04
@cgorenflocgorenflo
opened #2166
freeze-wasm
Status Failure
Total duration 1m 22s
Artifacts –

test.yaml

on: pull_request
test
1m 13s
test
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 1 warning
test: x/nexus/keeper/msg_server.go#L19
wasm already declared through import of package wasm ("github.com/CosmWasm/wasmd/x/wasm")
test: x/nexus/keeper/general_message.go#L8
other declaration of wasm
test: x/nexus/types/mock/expected_keepers.go#L21
cannot use &NexusMock{} (value of type *NexusMock) as "github.com/axelarnetwork/axelar-core/x/nexus/types".Nexus value in variable declaration: *NexusMock does not implement "github.com/axelarnetwork/axelar-core/x/nexus/types".Nexus (missing method ActivateWasmConnection)
test: x/nexus/keeper/msg_server.go#L19
wasm already declared through import of package wasm ("github.com/CosmWasm/wasmd/x/wasm")
test: x/nexus/keeper/general_message.go#L8
other declaration of wasm
test
Process completed with exit code 1.
test
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-go@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/