This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 20 succeeded
Started2022-09-22 05:01
Elapsed1h13m
Revisionmain

Test Failures


capa-e2e [unmanaged] [functional] GPU-enabled cluster test should create cluster with single worker 23m51s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capa\-e2e\s\[unmanaged\]\s\[functional\]\sGPU\-enabled\scluster\stest\sshould\screate\scluster\swith\ssingle\sworker$'
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:116
Timed out after 600.067s.
Job default/cuda-vector-add failed
Job:
{
  "metadata": {
    "name": "cuda-vector-add",
    "namespace": "default",
    "uid": "282d41cc-becf-4d02-a512-87bc7e3b13b5",
    "resourceVersion": "990",
    "generation": 1,
    "creationTimestamp": "2022-09-22T05:25:30Z",
    "labels": {
      "controller-uid": "282d41cc-becf-4d02-a512-87bc7e3b13b5",
      "job-name": "cuda-vector-add"
    },
    "managedFields": [
      {
        "manager": "cluster-api-e2e",
        "operation": "Update",
        "apiVersion": "batch/v1",
        "time": "2022-09-22T05:25:30Z",
        "fieldsType": "FieldsV1",
        "fieldsV1": {
          "f:spec": {
            "f:backoffLimit": {},
            "f:completionMode": {},
            "f:completions": {},
            "f:parallelism": {},
            "f:suspend": {},
            "f:template": {
              "f:spec": {
                "f:containers": {
                  "k:{\"name\":\"cuda-vector-add\"}": {
                    ".": {},
                    "f:image": {},
                    "f:imagePullPolicy": {},
                    "f:name": {},
                    "f:resources": {
                      ".": {},
                      "f:limits": {
                        ".": {},
                        "f:nvidia.com/gpu": {}
                      }
                    },
                    "f:terminationMessagePath": {},
                    "f:terminationMessagePolicy": {}
                  }
                },
                "f:dnsPolicy": {},
                "f:restartPolicy": {},
                "f:schedulerName": {},
                "f:securityContext": {},
                "f:terminationGracePeriodSeconds": {}
              }
            }
          }
        }
      },
      {
        "manager": "kube-controller-manager",
        "operation": "Update",
        "apiVersion": "batch/v1",
        "time": "2022-09-22T05:25:30Z",
        "fieldsType": "FieldsV1",
        "fieldsV1": {
          "f:status": {
            "f:active": {},
            "f:ready": {},
            "f:startTime": {}
          }
        },
        "subresource": "status"
      }
    ]
  },
  "spec": {
    "parallelism": 1,
    "completions": 1,
    "backoffLimit": 6,
    "selector": {
      "matchLabels": {
        "controller-uid": "282d41cc-becf-4d02-a512-87bc7e3b13b5"
      }
    },
    "template": {
      "metadata": {
        "creationTimestamp": null,
        "labels": {
          "controller-uid": "282d41cc-becf-4d02-a512-87bc7e3b13b5",
          "job-name": "cuda-vector-add"
        }
      },
      "spec": {
        "containers": [
          {
            "name": "cuda-vector-add",
            "image": "nvcr.io/nvidia/k8s/cuda-sample:vectoradd-cuda11.1-ubuntu18.04",
            "resources": {
              "limits": {
                "nvidia.com/gpu": "1"
              }
            },
            "terminationMessagePath": "/dev/termination-log",
            "terminationMessagePolicy": "File",
            "imagePullPolicy": "IfNotPresent"
          }
        ],
        "restartPolicy": "OnFailure",
        "terminationGracePeriodSeconds": 30,
        "dnsPolicy": "ClusterFirst",
        "securityContext": {},
        "schedulerName": "default-scheduler"
      }
    },
    "completionMode": "NonIndexed",
    "suspend": false
  },
  "status": {
    "startTime": "2022-09-22T05:25:30Z",
    "active": 1,
    "ready": 0
  }
}
LAST SEEN                      TYPE    REASON            OBJECT               MESSAGE
2022-09-22 05:25:30 +0000 UTC  Normal  SuccessfulCreate  job/cuda-vector-add  Created pod: cuda-vector-add-sk9s8

Expected
    <bool>: false
to be true
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/shared/gpu.go:134
				
				Click to see stdout/stderrfrom junit.e2e_suite.9.xml

Filter through log files | View test history on testgrid


Show 20 Passed Tests

Show 8 Skipped Tests

Error lines from build-log.txt

... skipping 1830 lines ...
[12]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:163
[12] ------------------------------
[12] 
[12] JUnit report was created: /logs/artifacts/junit.e2e_suite.12.xml
[12] 
[12] Ran 1 of 1 Specs in 1461.937 seconds
[12] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[12] PASS
[13] INFO: Waiting for the cluster to be reconciled after moving back to booststrap
[13] STEP: Waiting for cluster to enter the provisioned phase
[13] STEP: Dumping logs from the "self-hosted-zt2d03" workload cluster
[13] STEP: Dumping all the Cluster API resources in the "self-hosted-fxxh5q" namespace
[13] STEP: Deleting cluster self-hosted-fxxh5q/self-hosted-zt2d03
... skipping 13 lines ...
[2]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:500
[2] ------------------------------
[2] 
[2] JUnit report was created: /logs/artifacts/junit.e2e_suite.2.xml
[2] 
[2] Ran 1 of 1 Specs in 1504.711 seconds
[2] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[2] PASS
[3] STEP: Node 3 acquired resources: {ec2-normal:0, vpc:2, eip:2, ngw:2, igw:2, classiclb:2, ec2-GPU:0, volume-gp2:0}
[3] [BeforeEach] Clusterctl Upgrade Spec [from latest v1beta1 release to v1beta2]
[3]   /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/clusterctl_upgrade.go:122
[3] STEP: Creating a namespace for hosting the "clusterctl-upgrade" test spec
[3] INFO: Creating namespace clusterctl-upgrade-65fc5p
... skipping 48 lines ...
[5]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:709
[5] ------------------------------
[5] 
[5] JUnit report was created: /logs/artifacts/junit.e2e_suite.5.xml
[5] 
[5] Ran 1 of 3 Specs in 1609.749 seconds
[5] SUCCESS! -- 1 Passed | 0 Failed | 2 Pending | 0 Skipped
[5] PASS
[19] STEP: Node 19 released resources: {ec2-normal:0, vpc:1, eip:3, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0}
[19] [AfterEach] [unmanaged] [Cluster API Framework] [smoke] [PR-Blocking]
[19]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_CAPI_quick_test.go:69
[19] STEP: Dumping all the Cluster API resources in the "capi-quick-start-kkhs7x" namespace
[8] STEP: Node 8 acquired resources: {ec2-normal:0, vpc:2, eip:2, ngw:2, igw:2, classiclb:2, ec2-GPU:0, volume-gp2:0}
... skipping 23 lines ...
[19]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/quick_start.go:77
[19] ------------------------------
[19] 
[19] JUnit report was created: /logs/artifacts/junit.e2e_suite.19.xml
[19] 
[19] Ran 1 of 3 Specs in 1611.546 seconds
[19] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 2 Skipped
[19] PASS
[8] cluster.cluster.x-k8s.io/k8s-upgrade-and-conformance-gkuc47 created
[8] awscluster.infrastructure.cluster.x-k8s.io/k8s-upgrade-and-conformance-gkuc47 created
[8] kubeadmcontrolplane.controlplane.cluster.x-k8s.io/k8s-upgrade-and-conformance-gkuc47-control-plane created
[8] awsmachinetemplate.infrastructure.cluster.x-k8s.io/k8s-upgrade-and-conformance-gkuc47-control-plane created
[8] machinedeployment.cluster.x-k8s.io/k8s-upgrade-and-conformance-gkuc47-md-0 created
... skipping 69 lines ...
[16]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:466
[16] ------------------------------
[16] 
[16] JUnit report was created: /logs/artifacts/junit.e2e_suite.16.xml
[16] 
[16] Ran 1 of 1 Specs in 1668.979 seconds
[16] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[16] PASS
[10] STEP: Node 10 acquired resources: {ec2-normal:0, vpc:2, eip:2, ngw:2, igw:2, classiclb:2, ec2-GPU:0, volume-gp2:0}
[10] [BeforeEach] Cluster Upgrade Spec - HA control plane with scale in rollout [K8s-Upgrade]
[10]   /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/cluster_upgrade.go:83
[10] STEP: Creating a namespace for hosting the "k8s-upgrade-and-conformance" test spec
[10] INFO: Creating namespace k8s-upgrade-and-conformance-06soam
... skipping 40 lines ...
[9]   GPU-enabled cluster test
[9]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:115
[9]     should create cluster with single worker [It]
[9]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:116
[9] 
[9]     Timed out after 600.067s.
[9]     Job default/cuda-vector-add failed
[9]     Job:
[9]     {
[9]       "metadata": {
[9]         "name": "cuda-vector-add",
[9]         "namespace": "default",
[9]         "uid": "282d41cc-becf-4d02-a512-87bc7e3b13b5",
... skipping 189 lines ...
[6] INFO: Getting the cluster template yaml
[6] INFO: clusterctl config cluster k8s-upgrade-and-conformance-r6rhyp --infrastructure (default) --kubernetes-version v1.23.6 --control-plane-machine-count 3 --worker-machine-count 0 --flavor (default)
[17] 
[17] JUnit report was created: /logs/artifacts/junit.e2e_suite.17.xml
[17] 
[17] Ran 1 of 1 Specs in 1799.504 seconds
[17] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[17] PASS
[6] INFO: Applying the cluster template yaml to the cluster
[6] cluster.cluster.x-k8s.io/k8s-upgrade-and-conformance-r6rhyp created
[6] awscluster.infrastructure.cluster.x-k8s.io/k8s-upgrade-and-conformance-r6rhyp created
[6] kubeadmcontrolplane.controlplane.cluster.x-k8s.io/k8s-upgrade-and-conformance-r6rhyp-control-plane created
[6] awsmachinetemplate.infrastructure.cluster.x-k8s.io/k8s-upgrade-and-conformance-r6rhyp-control-plane created
... skipping 51 lines ...
[15]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/mhc_remediations.go:82
[15] ------------------------------
[15] 
[15] JUnit report was created: /logs/artifacts/junit.e2e_suite.15.xml
[15] 
[15] Ran 1 of 1 Specs in 1850.841 seconds
[15] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[15] PASS
[10] INFO: Waiting for control plane to be initialized
[10] INFO: Waiting for the first control plane machine managed by k8s-upgrade-and-conformance-06soam/k8s-upgrade-and-conformance-swd0v5-control-plane to be provisioned
[10] STEP: Waiting for one control plane node to exist
[11] STEP: Deleting namespace used for hosting the "" test spec
[11] INFO: Deleting namespace functional-test-multi-az-0pkytk
... skipping 8 lines ...
[11]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:551
[11] ------------------------------
[11] 
[11] JUnit report was created: /logs/artifacts/junit.e2e_suite.11.xml
[11] 
[11] Ran 1 of 1 Specs in 1891.987 seconds
[11] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[11] PASS
[13] STEP: Deleting namespace used for hosting the "self-hosted" test spec
[13] INFO: Deleting namespace self-hosted-fxxh5q
[13] [AfterEach] Self Hosted Spec
[13]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_CAPI_test.go:108
[13] STEP: Node 13 released resources: {ec2-normal:0, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0}
... skipping 7 lines ...
[13]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/self_hosted.go:80
[13] ------------------------------
[13] 
[13] JUnit report was created: /logs/artifacts/junit.e2e_suite.13.xml
[13] 
[13] Ran 1 of 1 Specs in 1915.985 seconds
[13] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[13] PASS
[3] STEP: Checking all the machines controlled by clusterctl-upgrade-ko38le-md-0 are in the "<None>" failure domain
[3] INFO: Waiting for the machine pools to be provisioned
[3] STEP: Turning the workload cluster into a management cluster with older versions of providers
[3] INFO: Downloading clusterctl binary from https://github.com/kubernetes-sigs/cluster-api/releases/download/v1.2.0/clusterctl-linux-amd64
[3] STEP: Initializing the workload cluster with older versions of providers
... skipping 68 lines ...
[18]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/mhc_remediations.go:114
[18] ------------------------------
[18] 
[18] JUnit report was created: /logs/artifacts/junit.e2e_suite.18.xml
[18] 
[18] Ran 1 of 1 Specs in 2048.704 seconds
[18] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[18] PASS
[6] INFO: Waiting for control plane to be ready
[6] INFO: Waiting for the remaining control plane machines managed by k8s-upgrade-and-conformance-l0vy9f/k8s-upgrade-and-conformance-r6rhyp-control-plane to be provisioned
[6] STEP: Waiting for all control plane nodes to exist
[4] STEP: Deleting retained dynamically provisioned volumes
[4] STEP: Deleting dynamically provisioned volumes
... skipping 16 lines ...
[4]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:397
[4] ------------------------------
[4] 
[4] JUnit report was created: /logs/artifacts/junit.e2e_suite.4.xml
[4] 
[4] Ran 1 of 1 Specs in 2093.783 seconds
[4] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[4] PASS
[10] INFO: Waiting for control plane k8s-upgrade-and-conformance-06soam/k8s-upgrade-and-conformance-swd0v5-control-plane to be ready (implies underlying nodes to be ready as well)
[10] STEP: Waiting for the control plane to be ready
[10] STEP: Checking all the the control plane machines are in the expected failure domains
[10] INFO: Waiting for the machine deployments to be provisioned
[10] STEP: Waiting for the workload nodes to exist
... skipping 24 lines ...
[7]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:328
[7] ------------------------------
[7] 
[7] JUnit report was created: /logs/artifacts/junit.e2e_suite.7.xml
[7] 
[7] Ran 1 of 1 Specs in 2143.746 seconds
[7] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[7] PASS
[6] INFO: Waiting for control plane k8s-upgrade-and-conformance-l0vy9f/k8s-upgrade-and-conformance-r6rhyp-control-plane to be ready (implies underlying nodes to be ready as well)
[6] STEP: Waiting for the control plane to be ready
[6] STEP: Checking all the the control plane machines are in the expected failure domains
[6] INFO: Waiting for the machine deployments to be provisioned
[6] STEP: Waiting for the workload nodes to exist
... skipping 24 lines ...
[20]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:260
[20] ------------------------------
[20] 
[20] JUnit report was created: /logs/artifacts/junit.e2e_suite.20.xml
[20] 
[20] Ran 1 of 2 Specs in 2234.181 seconds
[20] SUCCESS! -- 1 Passed | 0 Failed | 1 Pending | 0 Skipped
[20] PASS
[9] STEP: Deleting namespace used for hosting the "" test spec
[9] INFO: Deleting namespace functional-gpu-cluster-swuaid
[9] 
[9] JUnit report was created: /logs/artifacts/junit.e2e_suite.9.xml
[9] 
[9] 
[9] Summarizing 1 Failure:
[9] 
[9] [Fail] [unmanaged] [functional] GPU-enabled cluster test [It] should create cluster with single worker 
[9] /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/shared/gpu.go:134
[9] 
[9] Ran 1 of 1 Specs in 2255.658 seconds
[9] FAIL! -- 0 Passed | 1 Failed | 0 Pending | 0 Skipped
[9] --- FAIL: TestE2E (2255.72s)
[9] FAIL
[3] STEP: THE MANAGEMENT CLUSTER WITH OLDER VERSION OF PROVIDERS WORKS!
[3] STEP: Upgrading providers to the latest version available
[3] INFO: clusterctl upgrade apply --contract v1beta1
[3] INFO: Waiting for provider controllers to be running
[3] STEP: Waiting for deployment capa-system/capa-controller-manager to be available
[3] INFO: Creating log watcher for controller capa-system/capa-controller-manager, pod capa-controller-manager-7b68686c58-g29tk, container manager
... skipping 48 lines ...
[14]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/machine_pool.go:76
[14] ------------------------------
[14] 
[14] JUnit report was created: /logs/artifacts/junit.e2e_suite.14.xml
[14] 
[14] Ran 1 of 1 Specs in 2813.807 seconds
[14] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[14] PASS
[8] STEP: Upgrading the machinepool instances
[8] INFO: Patching the new Kubernetes version to Machine Pool k8s-upgrade-and-conformance-kn9064/k8s-upgrade-and-conformance-gkuc47-mp-0
[8] INFO: Waiting for Kubernetes versions of machines in MachinePool k8s-upgrade-and-conformance-kn9064/k8s-upgrade-and-conformance-gkuc47-mp-0 to be upgraded from v1.23.6 to v1.24.0
[8] INFO: Ensuring all MachinePool Instances have upgraded kubernetes version v1.24.0
[3] STEP: Deleting cluster clusterctl-upgrade/clusterctl-upgrade-ko38le
... skipping 62 lines ...
[3]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/clusterctl_upgrade.go:147
[3] ------------------------------
[3] 
[3] JUnit report was created: /logs/artifacts/junit.e2e_suite.3.xml
[3] 
[3] Ran 1 of 1 Specs in 3415.122 seconds
[3] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[3] PASS
[10] STEP: Deleting namespace used for hosting the "k8s-upgrade-and-conformance" test spec
[10] INFO: Deleting namespace k8s-upgrade-and-conformance-06soam
[10] 
[10] • [SLOW TEST:3113.227 seconds]
[10] [unmanaged] [Cluster API Framework]
... skipping 4 lines ...
[10]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/cluster_upgrade.go:117
[10] ------------------------------
[10] 
[10] JUnit report was created: /logs/artifacts/junit.e2e_suite.10.xml
[10] 
[10] Ran 1 of 1 Specs in 3463.257 seconds
[10] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[10] PASS
[6] STEP: Deleting namespace used for hosting the "k8s-upgrade-and-conformance" test spec
[6] INFO: Deleting namespace k8s-upgrade-and-conformance-l0vy9f
[6] [AfterEach] Cluster Upgrade Spec - HA Control Plane Cluster [K8s-Upgrade]
[6]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_CAPI_test.go:208
[6] STEP: Node 6 released resources: {ec2-normal:0, vpc:2, eip:2, ngw:2, igw:2, classiclb:2, ec2-GPU:0, volume-gp2:0}
... skipping 15 lines ...
[6] STEP: Deleting namespace used for hosting the "" test spec
[6] INFO: Deleting namespace functional-test-ignition-dt0rzw
[6] 
[6] JUnit report was created: /logs/artifacts/junit.e2e_suite.6.xml
[6] 
[6] Ran 2 of 3 Specs in 3719.148 seconds
[6] SUCCESS! -- 2 Passed | 0 Failed | 1 Pending | 0 Skipped
[6] PASS
[8] STEP: Deleting namespace used for hosting the "k8s-upgrade-and-conformance" test spec
[8] INFO: Deleting namespace k8s-upgrade-and-conformance-kn9064
[8] [AfterEach] Cluster Upgrade Spec - Single control plane with workers [K8s-Upgrade]
[8]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_CAPI_test.go:158
[8] STEP: Node 8 released resources: {ec2-normal:0, vpc:2, eip:2, ngw:2, igw:2, classiclb:2, ec2-GPU:0, volume-gp2:0}
... skipping 7 lines ...
[8]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/cluster_upgrade.go:117
[8] ------------------------------
[8] 
[8] JUnit report was created: /logs/artifacts/junit.e2e_suite.8.xml
[8] 
[8] Ran 1 of 1 Specs in 3762.055 seconds
[8] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[8] PASS
[1] folder created for eks clusters: /logs/artifacts/clusters/bootstrap/aws-resources
[1] STEP: Tearing down the management cluster
[1] STEP: Deleting cluster-api-provider-aws-sigs-k8s-io CloudFormation stack
[1] 
[1] JUnit report was created: /logs/artifacts/junit.e2e_suite.1.xml
[1] 
[1] Ran 1 of 3 Specs in 4118.212 seconds
[1] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 2 Skipped
[1] PASS

Ginkgo ran 1 suite in 1h10m38.440735187s
Test Suite Failed

Ginkgo 2.0 is coming soon!
==========================
Ginkgo 2.0 is under active development and will introduce several new features, improvements, and a small handful of breaking changes.
A release candidate for 2.0 is now available and 2.0 should GA in Fall 2021.  Please give the RC a try and send us feedback!
  - To learn more, view the migration guide at https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md
... skipping 3 lines ...
To silence this notice, set the environment variable: ACK_GINKGO_RC=true
Alternatively you can: touch $HOME/.ack-ginkgo-rc

real	70m38.457s
user	26m19.403s
sys	6m59.410s
make: *** [Makefile:401: test-e2e] Error 1
+ EXIT_VALUE=2
+ set +o xtrace
Cleaning up after docker in docker.
================================================================================
Cleaning up after docker
Stopping Docker: dockerProgram process in pidfile '/var/run/docker-ssd.pid', 1 process(es), refused to die.
... skipping 3 lines ...