SUITE=./test/conformance ./hack/run-e2e-conformance.sh
/usr/local/bin/ginkgo
[38;5;9m[1mGinkgo detected a version mismatch between the Ginkgo CLI and the version of Ginkgo imported by your packages:[0m
  Ginkgo CLI Version:
    [1m2.4.0[0m
  Mismatched package versions found:
    [1m2.9.4[0m used by conformance

  [38;5;243mGinkgo will continue to attempt to run but you may see errors (including flag
  parsing errors) and should either update your go.mod or your version of the
  Ginkgo CLI to match.

  To install the matching version of the CLI run
    [1mgo install github.com/onsi/ginkgo/v2/ginkgo[0m[38;5;243m
  from a path that contains a go.mod file.  Alternatively you can use
    [1mgo run github.com/onsi/ginkgo/v2/ginkgo[0m[38;5;243m
  from a path that contains a go.mod file to invoke the matching version of the
  Ginkgo CLI.

  If you are attempting to test multiple packages that each have a different
  version of the Ginkgo library with a single Ginkgo CLI that is currently
  unsupported.
  [0m
Running Suite: SRIOV Operator conformance tests - /home/apanatto/dev/github.com/k8snetworkplumbingwg/sriov-network-operator/test/conformance
============================================================================================================================================
Random Seed: [1m1690963002[0m

Will run [1m2[0m of [1m29[0m specs
[38;5;14mS[0m[38;5;14mS[0m[38;5;14mS[0m[38;5;14mS[0m[38;5;14mS[0m[38;5;14mS[0m[38;5;14mS[0m[38;5;14mS[0m[38;5;14mS[0m[38;5;14mS[0m[38;5;14mS[0m[38;5;14mS[0m[38;5;14mS[0m[38;5;14mS[0m[38;5;14mS[0m[38;5;14mS[0m[38;5;14mS[0m[38;5;14mS[0m[38;5;14mS[0m[38;5;14mS[0m[38;5;14mS[0mWaiting for the sriov state to stable
Sriov state is stable
W0802 09:57:02.484049 1106716 warnings.go:70] would violate PodSecurity "restricted:latest": privileged (container "test" must not set securityContext.privileged=true), allowPrivilegeEscalation != false (container "test" must set securityContext.allowPrivilegeEscalation=false), unrestricted capabilities (container "test" must set securityContext.capabilities.drop=["ALL"]), restricted volume types (volume "host" uses restricted volume type "hostPath"), runAsNonRoot != true (pod or container "test" must set securityContext.runAsNonRoot=true), seccompProfile (pod or container "test" must set securityContext.seccompProfile.type to "RuntimeDefault" or "Localhost")
Waiting for the sriov state to stable
Sriov state is stable
[38;5;10m•[0mWaiting for the sriov state to stable
Sriov state is stable
[38;5;10m•[0m[38;5;14mS[0m[38;5;14mS[0m[38;5;14mS[0m[38;5;14mS[0m[38;5;14mS[0m[38;5;14mS[0m

[38;5;10m[1mRan 2 of 29 Specs in 163.567 seconds[0m
[38;5;10m[1mSUCCESS![0m -- [38;5;10m[1m2 Passed[0m | [38;5;9m[1m0 Failed[0m | [38;5;11m[1m0 Pending[0m | [38;5;14m[1m27 Skipped[0m
PASS | FOCUSED
[38;5;228mYou're using deprecated Ginkgo functionality:[0m
[38;5;228m=============================================[0m
  [38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo.  This feature has proved to be more noisy than useful.  You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.[0m

[38;5;243mTo silence deprecations that can be silenced set the following environment variable:[0m
  [38;5;243mACK_GINKGO_DEPRECATIONS=2.9.4[0m


Ginkgo ran 1 suite in 2m48.548377743s
Test Suite Passed
Detected Programmatic Focus - setting exit status to 197