-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[flaky] test/e2e.TestBrokerTrigger/2 #127
Comments
Latest result for this test: Flaky 2020-09-13 10:59:30 +0000 UTC: ✔ ✖ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ Passed ✖ Failed ◻ Skipped |
{
"apiVersion": "eventing.knative.dev/v1beta1",
"kind": "Trigger",
"metadata": {
"annotations": {
"eventing.knative.dev/creator": "prow-job@knative-tests.iam.gserviceaccount.com",
"eventing.knative.dev/lastModifier": "prow-job@knative-tests.iam.gserviceaccount.com"
},
"creationTimestamp": "2020-08-26T10:27:27Z",
"finalizers": [
"kafka.triggers.eventing.knative.dev"
],
"generation": 1,
"labels": {
"eventing.knative.dev/broker": "broker"
},
"name": "trigger",
"namespace": "test-broker-trigger-2-ntsbg",
"resourceVersion": "11347",
"selfLink": "/apis/eventing.knative.dev/v1beta1/namespaces/test-broker-trigger-2-ntsbg/triggers/trigger",
"uid": "ffb57f43-e6ee-4bd7-92cf-d620fb0c0f11"
},
"spec": {
"broker": "broker",
"filter": {
"attributes": {
"ext1": "value1",
"source": "source1",
"type": ""
}
},
"subscriber": {
"ref": {
"apiVersion": "v1",
"kind": "Service",
"name": "subscriber",
"namespace": "test-broker-trigger-2-ntsbg"
}
}
},
"status": {}
} |
Closing issue: this test has passed in latest 2 scans |
Reopening issue: this test is flaky |
/close |
@pierDipi: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
When we probe for resource status, we want to avoid probing the pod when the status is in our expected status. Before this patch, we had an hard-coded expected status of `StatusReady`, which is wrong in the `FinalizeKind` case. Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>
Auto-generated issue tracking flakiness of test
The text was updated successfully, but these errors were encountered: