Adding missing UTs for Source reconcilers#2828
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nachocano The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
mattmoor
left a comment
There was a problem hiding this comment.
Produced via:
gofmt -s -w $(find -path './vendor' -prune -o -path './third_party' -prune -o -type f -name '*.go' -print)
| }, | ||
| }, | ||
| //}, { | ||
| // TODO uncomment the following once we figure out why the eventtype informer is missing from the duck.controller. |
There was a problem hiding this comment.
@n3wscott I'm having trouble with this one.
It seems that the context we pass to the Source duck controller doesn't have eventtype:
eventing/pkg/reconciler/source/crd/crd.go
Line 203 in 7dca1df
I might be missing something, OR there is a bug in
eventing/pkg/reconciler/source/crd/crd.go
Line 201 in 7dca1df
Any ideas?
There was a problem hiding this comment.
What is the error that is thrown?
There was a problem hiding this comment.
does it not have the kind EventType? I need more info to try to help
There was a problem hiding this comment.
sorrry, was AFK...
The problem that the informer is not registered: Unable to fetch knative.dev/eventing/pkg/client/informers/externalversions/eventing/v1alpha1.EventTypeInformer from context
updated the codegen stuff... will be back in a few mins
|
/retest
…On Tue, Mar 24, 2020 at 8:43 AM Knative Prow Robot ***@***.***> wrote:
@nachocano <https://github.com/nachocano>: The following tests *failed*,
say /retest to rerun all failed tests:
Test name Commit Details Rerun command
pull-knative-eventing-unit-tests 9cb4b29
<9cb4b29>
link
<https://prow.knative.dev/view/gcs/knative-prow/pr-logs/pull/knative_eventing/2828/pull-knative-eventing-unit-tests/1242475697180512258> /test
pull-knative-eventing-unit-tests
pull-knative-eventing-go-coverage 9cb4b29
<9cb4b29>
link
<https://prow.knative.dev/view/gcs/knative-prow/pr-logs/pull/knative_eventing/2828/pull-knative-eventing-go-coverage/1242475697180512257> /test
pull-knative-eventing-go-coverage
Full PR test history
<https://gubernator.knative.dev/pr/knative_eventing/2828>. Your PR
dashboard <https://gubernator.knative.dev/pr/nachocano>.
Instructions for interacting with me using PR comments are available here
<https://git.k8s.io/community/contributors/guide/pull-requests.md>. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
<https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:>
repository. I understand the commands that are listed here
<https://go.k8s.io/bot-commands>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2828 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABD65DEF3EMBL7HIUUC4TT3RJDIIZANCNFSM4LSX33PA>
.
|
|
looks like you got a |
|
/retest |
|
hmmm |
|
The following is the coverage report on the affected files.
|
|
@nachocano: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. I understand the commands that are listed here. |
|
@n3wscott mind if we get this one in as in and we keep on debugging that one to further increase the coverage? |
|
/lgtm |
Proposed Changes
Release Note
Docs
/assign @n3wscott