This job view page is being replaced by Spyglass soon. Check out the new job view.
PRsedefsavas: v1beta2 APIs
ResultFAILURE
Tests 0 failed / 1 succeeded
Started2022-09-15 17:34
Elapsed44m35s
Revision442450d35ed1ab5ceef57ce09b0f3a1a923e081f
Refs 3720

No Test Failures!


Show 1 Passed Tests

Show 28 Skipped Tests

Error lines from build-log.txt

... skipping 559 lines ...
[6] STEP: Setting environment variable: key=AWS_SSH_KEY_NAME, value=cluster-api-provider-aws-sigs-k8s-io
[6] STEP: Setting environment variable: key=AWS_B64ENCODED_CREDENTIALS, value=*******
[6] 
[6] JUnit report was created: /logs/artifacts/junit.e2e_suite.6.xml
[6] 
[6] Ran 0 of 0 Specs in 335.480 seconds
[6] SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 0 Skipped
[6] PASS | FOCUSED
[2] STEP: Setting environment variable: key=AWS_AVAILABILITY_ZONE_1, value=us-west-2a
[2] STEP: Setting environment variable: key=AWS_AVAILABILITY_ZONE_2, value=us-west-2b
[2] STEP: Setting environment variable: key=AWS_REGION, value=us-west-2
[2] STEP: Setting environment variable: key=AWS_SSH_KEY_NAME, value=cluster-api-provider-aws-sigs-k8s-io
[2] STEP: Setting environment variable: key=AWS_B64ENCODED_CREDENTIALS, value=*******
[2] 
[2] JUnit report was created: /logs/artifacts/junit.e2e_suite.2.xml
[2] 
[2] Ran 0 of 0 Specs in 335.491 seconds
[2] SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 0 Skipped
[2] PASS | FOCUSED
[5] STEP: Setting environment variable: key=AWS_AVAILABILITY_ZONE_1, value=us-west-2a
[5] STEP: Setting environment variable: key=AWS_AVAILABILITY_ZONE_2, value=us-west-2b
[5] STEP: Setting environment variable: key=AWS_REGION, value=us-west-2
[5] STEP: Setting environment variable: key=AWS_SSH_KEY_NAME, value=cluster-api-provider-aws-sigs-k8s-io
[5] STEP: Setting environment variable: key=AWS_B64ENCODED_CREDENTIALS, value=*******
[5] 
[5] JUnit report was created: /logs/artifacts/junit.e2e_suite.5.xml
[5] 
[5] Ran 0 of 0 Specs in 335.498 seconds
[5] SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 0 Skipped
[5] PASS | FOCUSED
[3] STEP: Setting environment variable: key=AWS_AVAILABILITY_ZONE_1, value=us-west-2a
[3] STEP: Setting environment variable: key=AWS_AVAILABILITY_ZONE_2, value=us-west-2b
[3] STEP: Setting environment variable: key=AWS_REGION, value=us-west-2
[3] STEP: Setting environment variable: key=AWS_SSH_KEY_NAME, value=cluster-api-provider-aws-sigs-k8s-io
[3] STEP: Setting environment variable: key=AWS_B64ENCODED_CREDENTIALS, value=*******
[3] 
[3] JUnit report was created: /logs/artifacts/junit.e2e_suite.3.xml
[3] 
[3] Ran 0 of 0 Specs in 335.523 seconds
[3] SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 0 Skipped
[3] PASS | FOCUSED
[4] STEP: Setting environment variable: key=AWS_AVAILABILITY_ZONE_1, value=us-west-2a
[4] STEP: Setting environment variable: key=AWS_AVAILABILITY_ZONE_2, value=us-west-2b
[4] STEP: Setting environment variable: key=AWS_REGION, value=us-west-2
[4] STEP: Setting environment variable: key=AWS_SSH_KEY_NAME, value=cluster-api-provider-aws-sigs-k8s-io
[4] STEP: Setting environment variable: key=AWS_B64ENCODED_CREDENTIALS, value=*******
[4] 
[4] JUnit report was created: /logs/artifacts/junit.e2e_suite.4.xml
[4] 
[4] Ran 0 of 0 Specs in 335.522 seconds
[4] SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 0 Skipped
[4] PASS | FOCUSED
[7] STEP: Node 7 acquired resources: {ec2-normal:0, vpc:2, eip:2, ngw:2, igw:2, classiclb:2, ec2-GPU:0, volume-gp2:0}
[7] [BeforeEach] Clusterctl Upgrade Spec [from latest v1beta1 release to v1beta2]
[7]   /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/clusterctl_upgrade.go:122
[7] STEP: Creating a namespace for hosting the "clusterctl-upgrade" test spec
[7] INFO: Creating namespace clusterctl-upgrade-xpts5i
... skipping 112 lines ...
[7]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/clusterctl_upgrade.go:147
[7] ------------------------------
[7] 
[7] JUnit report was created: /logs/artifacts/junit.e2e_suite.7.xml
[7] 
[7] Ran 1 of 14 Specs in 2365.892 seconds
[7] SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 13 Skipped
[7] PASS | FOCUSED
[1] SSSSSSSSSSSSSSSfolder 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 0 of 15 Specs in 2420.797 seconds
[1] SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 15 Skipped
[1] PASS | FOCUSED

Ginkgo ran 1 suite in 41m59.721767852s
Test Suite Passed
Detected Programmatic Focus - setting exit status to 197

real	41m59.731s
user	11m2.965s
sys	2m33.607s
make: *** [Makefile:397: test-e2e] Error 197
+ 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 ...