This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 0 succeeded
Started2021-05-26 01:12
Elapsed31m27s
Revisionrelease-0.4

Test Failures


capz-e2e Conformance Tests conformance-tests 24m24s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\sConformance\sTests\sconformance\-tests$'
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:68
Timed out after 1200.000s.
Expected
    <bool>: false
to be true
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api@v0.3.14/test/framework/controlplane_helpers.go:144
				
				Click to see stdout/stderrfrom junit.e2e_suite.1.xml

Filter through log files | View test history on testgrid


Show 16 Skipped Tests

Error lines from build-log.txt

... skipping 602 lines ...
[1] INFO: Creating namespace conformance-tests-0rbqmd
[1] INFO: Creating event watcher for namespace "conformance-tests-0rbqmd"
[3] 
[3] JUnit report was created: /logs/artifacts/junit.e2e_suite.3.xml
[3] 
[3] Ran 0 of 0 Specs in 161.557 seconds
[3] SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 0 Skipped
[3] PASS
[2] 
[2] JUnit report was created: /logs/artifacts/junit.e2e_suite.2.xml
[2] 
[2] Ran 0 of 0 Specs in 161.549 seconds
[2] SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 0 Skipped
[2] PASS
[1] [Measure] conformance-tests
[1]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:68
[1] INFO: Creating the workload cluster with name "capz-conf-npxsym" using the "conformance-ci-artifacts" template (Kubernetes v1.22.0-alpha.2.162+91200bac44f009, 824652078000 control-plane machines, 824652078008 worker machines)
[1] INFO: Getting the cluster template yaml
[1] INFO: clusterctl config cluster capz-conf-npxsym --infrastructure (default) --kubernetes-version v1.22.0-alpha.2.162+91200bac44f009 --control-plane-machine-count 1 --worker-machine-count 5 --flavor conformance-ci-artifacts
... skipping 88 lines ...
[1]   testing.tRunner(0xc00045e600, 0x1ec30f0)
[1]   	/usr/local/go/src/testing/testing.go:909 +0xc9
[1]   created by testing.(*T).Run
[1]   	/usr/local/go/src/testing/testing.go:960 +0x350
[1] ------------------------------
[1] STEP: Tearing down the management cluster
[1] E0526 01:43:07.473853   18875 request.go:924] Unexpected error when reading response body: unexpected EOF
[1] 
[1] JUnit report was created: /logs/artifacts/junit.e2e_suite.1.xml
[1] 
[1] 
[1] Summarizing 1 Failure:
[1] 
[1] [Fail] Conformance Tests [Measurement] conformance-tests 
[1] /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api@v0.3.14/test/framework/controlplane_helpers.go:144
[1] 
[1] Ran 1 of 17 Specs in 1627.889 seconds
[1] FAIL! -- 0 Passed | 1 Failed | 0 Pending | 16 Skipped
[1] --- FAIL: TestE2E (1627.90s)
[1] FAIL

Ginkgo ran 1 suite in 28m15.563790583s
Test Suite Failed
make[2]: *** [Makefile:167: test-e2e-run] Error 1
make[2]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
make[1]: *** [Makefile:183: test-e2e-local] Error 2
make[1]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
make: *** [Makefile:192: test-conformance] Error 2
================ REDACTING LOGS ================
All sensitive variables are redacted
+ EXIT_VALUE=2
+ set +o xtrace
Cleaning up after docker in docker.
================================================================================
... skipping 5 lines ...