Skip to content

Bump from github.com/libopenstorage/openstoragev1.0.0 to github.com/l… #6291

Bump from github.com/libopenstorage/openstoragev1.0.0 to github.com/l…

Bump from github.com/libopenstorage/openstoragev1.0.0 to github.com/l… #6291

Triggered via pull request March 12, 2024 16:09
Status Failure
Total duration 12m 6s
Artifacts

ci.yaml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

14 errors and 2 warnings
test-and-verify
cannot find package "k8s.io/apimachinery/pkg/util/wait" in any of:
test-and-verify
cannot find package "k8s.io/apimachinery/pkg/apis/meta/v1" in any of:
test-and-verify
cannot find package "k8s.io/apimachinery/pkg/types" in any of:
test-and-verify
cannot find package "k8s.io/apimachinery/pkg/watch" in any of:
test-and-verify
cannot find package "k8s.io/api/autoscaling/v2" in any of:
test-and-verify
cannot find package "k8s.io/apimachinery/pkg/runtime" in any of:
test-and-verify
cannot find package "k8s.io/apimachinery/pkg/runtime/schema" in any of:
test-and-verify
cannot find package "k8s.io/apimachinery/pkg/runtime/serializer" in any of:
test-and-verify
cannot find package "k8s.io/apimachinery/pkg/util/runtime" in any of:
test-and-verify
cannot find package "k8s.io/client-go/rest" in any of:
test-and-verify
cannot use false (untyped bool constant) as map[string]string value in argument to driver.Detach
test-and-verify
not enough arguments in call to driver.Mount
test-and-verify
not enough arguments in call to driver.Unmount
test-and-verify
Process completed with exit code 1.
test-and-verify
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-go@v2, actions/checkout@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
test-and-verify
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2, actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/