Skip to content

update to keyforge and add sign and verify #129

update to keyforge and add sign and verify

update to keyforge and add sign and verify #129

Triggered via pull request September 7, 2023 18:57
Status Failure
Total duration 54s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

test.yaml

on: pull_request
test and coverage
45s
test and coverage
integration tests
26s
integration tests
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 2 warnings
integration tests: cmd/keyforge/key_management.go#L10
no required module provides package github.com/libp2p/go-libp2p-core/crypto; to add it:
integration tests: cmd/keyforge/key_management.go#L11
no required module provides package github.com/libp2p/go-libp2p-core/peer; to add it:
integration tests
Process completed with exit code 1.
test and coverage: cmd/keyforge/key_management.go#L10
no required module provides package github.com/libp2p/go-libp2p-core/crypto; to add it:
test and coverage: cmd/keyforge/key_management.go#L11
no required module provides package github.com/libp2p/go-libp2p-core/peer; to add it:
test and coverage
Process completed with exit code 1.
integration tests
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-go@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test and coverage
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-go@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/