This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 1 succeeded
Started2023-01-24 20:38
Elapsed6m28s
Revisionb7df7032c3efa43eeeab5fb126f1aadbf4a18f36

Test Failures

capa-eks-e2e [SynchronizedBeforeSuite] 2m0s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capa\-eks\-e2e\s\[SynchronizedBeforeSuite\]$'
[FAILED] Timed out after 120.756s.
Expected
    <bool>: false
to equal
    <bool>: true
In [SynchronizedBeforeSuite] at: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/shared/aws.go:419 @ 01/24/23 20:44:16.742

				
				Click to see stdout/stderrfrom junit.e2e_suite.xml

Filter through log files | View test history on testgrid

Show 1 Passed Tests

Error lines from build-log.txt

... skipping 2557 lines ...
  STEP: Event details for AWSIAMRoleEKSControlPlane : Resource: AWS::IAM::Role, Status: CREATE_IN_PROGRESS @ 01/24/23 20:44:16.741
  STEP: Event details for AWSIAMRoleEKSNodegroup : Resource: AWS::IAM::Role, Status: CREATE_IN_PROGRESS @ 01/24/23 20:44:16.741
  STEP: Event details for CAPAMultiTenancySimple : Resource: AWS::IAM::Role, Status: CREATE_IN_PROGRESS @ 01/24/23 20:44:16.741
  STEP: Event details for AWSIAMRoleNodes : Resource: AWS::IAM::Role, Status: CREATE_IN_PROGRESS @ 01/24/23 20:44:16.741
  STEP: Event details for AWSIAMRoleControlPlane : Resource: AWS::IAM::Role, Status: CREATE_IN_PROGRESS @ 01/24/23 20:44:16.741
  STEP: Event details for cluster-api-provider-aws-sigs-k8s-io : Resource: AWS::CloudFormation::Stack, Status: CREATE_IN_PROGRESS @ 01/24/23 20:44:16.741
  [FAILED] in [SynchronizedBeforeSuite] - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/shared/aws.go:419 @ 01/24/23 20:44:16.742
[SynchronizedBeforeSuite] [FAILED] [120.768 seconds]
[SynchronizedBeforeSuite] 
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/managed/managed_suite_test.go:58

  [FAILED] Timed out after 120.756s.
  Expected
      <bool>: false
  to equal
      <bool>: true
  In [SynchronizedBeforeSuite] at: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/shared/aws.go:419 @ 01/24/23 20:44:16.742

... skipping 17 lines ...
[SynchronizedAfterSuite] 
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/managed/managed_suite_test.go:64

  [PANICKED] Test Panicked
  In [SynchronizedAfterSuite] at: /usr/local/go/src/runtime/panic.go:260 @ 01/24/23 20:44:16.743

  runtime error: invalid memory address or nil pointer dereference

  Full Stack Trace
    github.com/aws/aws-sdk-go/service/eks.New({0x0?, 0x0?}, {0x0?, 0x24?, 0xc000428e80?})
    	/home/prow/go/pkg/mod/github.com/aws/aws-sdk-go@v1.44.145/service/eks/service.go:52 +0x41
    sigs.k8s.io/cluster-api-provider-aws/v2/test/e2e/shared.DumpEKSClusters({0x3291658?, 0xc00005a130?}, 0xc00074bb80)
    	/home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/shared/aws.go:873 +0x29b
... skipping 5 lines ...
[ReportAfterSuite] Autogenerated ReportAfterSuite for --junit-report
autogenerated by Ginkgo
[ReportAfterSuite] PASSED [0.016 seconds]
------------------------------

Summarizing 2 Failures:
  [FAIL] [SynchronizedBeforeSuite] 
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/shared/aws.go:419
  [PANICKED!] [SynchronizedAfterSuite] 
  /usr/local/go/src/runtime/panic.go:260

Ran 0 of 4 Specs in 120.769 seconds
FAIL! -- A BeforeSuite node failed so all tests were skipped.
--- FAIL: TestE2E (120.79s)
FAIL

Ginkgo ran 1 suite in 3m42.108690816s

Test Suite Failed

real	3m42.187s
user	9m20.799s
sys	1m25.578s
make: *** [Makefile:410: test-e2e-eks] 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 ...