Closed zhongduo closed 3 years ago
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: zhongduo
The full list of commands accepted by this bot can be found here.
The pull request process is described here
release v0.20 works without PR error for two runs.
Reverting before #2102 by git revert --no-commit 0c8c969d46f01a0ce0..HEAD
, tests passed.
Reverting after #2102 , tests passed
third run passed.
integration test failed with crashloop in net-istio: https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/google_knative-gcp/2123/pull-google-knative-gcp-integration-tests/1356964882360045568
/test pull-google-knative-gcp-integration-tests
wi failed with "message": "Ingress has not yet been reconciled.", "reason": "IngressNotConfigured",
.
/retest
The following is the coverage report on the affected files.
Say /test pull-google-knative-gcp-go-coverage
to re-run this coverage report
File | Old Coverage | New Coverage | Delta |
---|---|---|---|
pkg/broker/handler/processors/deliver/processor.go | 77.8% | 76.1% | -1.6 |
pkg/reconciler/broker/controller.go | 65.5% | 58.6% | -6.9 |
pkg/reconciler/brokercell/broker_targets_config.go | 76.8% | 75.9% | -0.9 |
pkg/reconciler/intevents/pullsubscription/keda/controller.go | 88.5% | 88.9% | 0.4 |
pkg/reconciler/intevents/pullsubscription/static/controller.go | 88.0% | 88.5% | 0.5 |
pkg/reconciler/intevents/topic/controller.go | 84.2% | 85.0% | 0.8 |
Integration test failed with "message": "Ingress has not yet been reconciled.", "reason": "IngressNotConfigured" https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/google_knative-gcp/2123/pull-google-knative-gcp-integration-tests/1356996345784700928
/retest
@zhongduo: PR needs rebase.
@zhongduo: The following tests failed, say /retest
to rerun all failed tests:
Test name | Commit | Details | Rerun command |
---|---|---|---|
pull-google-knative-gcp-unit-tests | 13d5d7b7777894bfd92299e99a23254ef3bf7cb2 | link | /test pull-google-knative-gcp-unit-tests |
pull-google-knative-gcp-build-tests | 13d5d7b7777894bfd92299e99a23254ef3bf7cb2 | link | /test pull-google-knative-gcp-build-tests |
pull-google-knative-gcp-go-coverage | 13d5d7b7777894bfd92299e99a23254ef3bf7cb2 | link | /test pull-google-knative-gcp-go-coverage |
pull-google-knative-gcp-integration-tests | 13d5d7b7777894bfd92299e99a23254ef3bf7cb2 | link | /test pull-google-knative-gcp-integration-tests |
pull-google-knative-gcp-conformance-tests | 13d5d7b7777894bfd92299e99a23254ef3bf7cb2 | link | /test pull-google-knative-gcp-conformance-tests |
pull-google-knative-gcp-wi-tests | 13d5d7b7777894bfd92299e99a23254ef3bf7cb2 | link | /test pull-google-knative-gcp-wi-tests |
pull-google-knative-gcp-upgrade-tests | 13d5d7b7777894bfd92299e99a23254ef3bf7cb2 | link | /test pull-google-knative-gcp-upgrade-tests |
Full PR test history. Your PR dashboard.
Problem not reproducible, but I believe it is related to GKE.
Fixes #
Proposed Changes
-
-
Release Note
Docs