Skip to content

Adding support in CNI for managing multiple network interface card on the instance #2147

Adding support in CNI for managing multiple network interface card on the instance

Adding support in CNI for managing multiple network interface card on the instance #2147

Triggered via pull request March 23, 2025 06:52
Status Failure
Total duration 6m 13s
Artifacts

pr-automated-tests.yaml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

11 errors
Unit test: cmd/aws-vpc-cni-init/main.go#L58
github.com/aws/amazon-vpc-cni-k8s/pkg/awsutils.TypedIMDS struct literal uses unkeyed fields
Unit test
too many arguments in call to n.SetupPodNetwork
Unit test
cannot use len(r.IPAddress) (value of type int) as int32 value in struct literal
Unit test
not enough arguments in call to cache.awsGetFreeDeviceNumber
Unit test
not enough arguments in call to GeneratePodHostVethName
Unit test
assignment mismatch: 4 variables but ds.UnassignPodIPAddress returns 5 values
Unit test
cannot use m.awsutils (variable of type *mock_awsutils.MockAPIs) as awsutils.APIs value in struct literal: *mock_awsutils.MockAPIs does not implement awsutils.APIs (wrong type for method AllocENI)
Unit test
Process completed with exit code 2.
Build Docker images
cannot use len(r.IPAddress) (value of type int) as int32 value in struct literal
Build Docker images
cannot use len(r.IPAddress) (value of type int) as int32 value in struct literal
Build Docker images
Process completed with exit code 2.