🤖 Triggering CI on branch 'release-next' after synching to upstream/master

[alanfx]

No description provided.

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alanfx

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [alanfx]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

@alanfx: The following tests failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
ci/prow/46-e2e-aws-ocp-46	f090321	link	/test 46-e2e-aws-ocp-46
ci/prow/e2e-aws-ocp-43	f090321	link	/test e2e-aws-ocp-43

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

[lberk]

/retest

[lberk]

/close
forgot to drop knative-eventing-channel-broker-ci.yaml from the catalogsource yaml

[openshift-ci-robot]

@lberk: Closed this PR.

Details

In response to this:

/close
forgot to drop knative-eventing-channel-broker-ci.yaml from the catalogsource yaml

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.