What happened?
Recently while running the v1.20 RC release process, I saw lots of failures across multiple test suites in the TestCrossplaneLifecycle test. There were also some successes too, so I don't think it's completely broken, just flaky.
Here's an example failure run: https://github.com/crossplane/crossplane/actions/runs/15014576478/job/42189514310. These logs have been copied to https://gist.github.com/jbw976/0486f485f4e3765882fc50d2b03c4ce2 for more durable storage.
Here's the final failure:
+e2e *failed* | install_test.go:47: resource did not have desired conditions: HealthyPackageRevision, ActivePackageRevision: context deadline exceeded:
+e2e *failed* |
+e2e *failed* | apiVersion: pkg.crossplane.io/v1
+e2e *failed* | kind: Provider
+e2e *failed* | metadata:
+e2e *failed* | creationTimestamp: null
+e2e *failed* | name: provider-nop
+e2e *failed* | spec:
+e2e *failed* | ignoreCrossplaneConstraints: true
+e2e *failed* | package: xpkg.upbound.io/crossplane-contrib/provider-nop:v0.3.0
+e2e *failed* | status: {}
+e2e *failed* |
+e2e *failed* |
+e2e *failed* | Related objects:
+e2e *failed* |
+e2e *failed* |
+e2e *failed* | --- FAIL: TestCrossplaneLifecycle/TestCrossplaneLifecycleUpgrade/ProviderIsReady (192.81s)
Also interesting that the test fails 3 times in a row (I don't have a ton of confidence in gotestsum rerun capability yet though, so perhaps don't read too much into this):
+e2e *failed* | === Failed
+e2e *failed* | === FAIL: E2E TestCrossplaneLifecycle/TestCrossplaneLifecycleUpgrade/ProviderIsReady (194.86s)
+e2e *failed* | === FAIL: E2E TestCrossplaneLifecycle/TestCrossplaneLifecycleUpgrade (207.55s)
+e2e *failed* | === FAIL: E2E TestCrossplaneLifecycle (280.49s)
+e2e *failed* | === FAIL: E2E TestCrossplaneLifecycle/TestCrossplaneLifecycleUpgrade/ProviderIsReady (re-run 1) (192.81s)
+e2e *failed* | === FAIL: E2E TestCrossplaneLifecycle/TestCrossplaneLifecycleUpgrade (re-run 1) (192.81s)
+e2e *failed* | === FAIL: E2E TestCrossplaneLifecycle (re-run 1) (192.81s)
+e2e *failed* | === FAIL: E2E TestCrossplaneLifecycle/TestCrossplaneLifecycleUpgrade/ProviderIsReady (re-run 2) (192.81s)
+e2e *failed* | === FAIL: E2E TestCrossplaneLifecycle/TestCrossplaneLifecycleUpgrade (re-run 2) (192.81s)
+e2e *failed* | === FAIL: E2E TestCrossplaneLifecycle (re-run 2) (192.81s)
What environment did it happen in?
Crossplane version: v1.20.0-rc.1
What happened?
Recently while running the v1.20 RC release process, I saw lots of failures across multiple test suites in the
TestCrossplaneLifecycletest. There were also some successes too, so I don't think it's completely broken, just flaky.Here's an example failure run: https://github.com/crossplane/crossplane/actions/runs/15014576478/job/42189514310. These logs have been copied to https://gist.github.com/jbw976/0486f485f4e3765882fc50d2b03c4ce2 for more durable storage.
Here's the final failure:
Also interesting that the test fails 3 times in a row (I don't have a ton of confidence in
gotestsumrerun capability yet though, so perhaps don't read too much into this):What environment did it happen in?
Crossplane version:
v1.20.0-rc.1