🤖 Triggering CI on branch 'release-next' after synching to upstream/main #341
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
[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
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
alanfx
force-pushed
the
release-next
branch
from
1552e86
to
5c4cbd9
Compare
alanfx
force-pushed
the
release-next-ci
branch
from
caf9c15
to
31dabcd
Compare
alanfx
force-pushed
the
release-next
branch
from
5c4cbd9
to
9d31a36
Compare
alanfx
force-pushed
the
release-next-ci
branch
from
31dabcd
to
efe998b
Compare
|
/retest |
|
When I run the I do get this: which does explain errors like: @mgencur is there something wrong with the |
|
/retest |
alanfx
force-pushed
the
release-next
branch
from
9d31a36
to
c0e5f6a
Compare
alanfx
force-pushed
the
release-next-ci
branch
from
efe998b
to
1e3d31b
Compare
alanfx
force-pushed
the
release-next
branch
from
c0e5f6a
to
5a5a1a6
Compare
alanfx
force-pushed
the
release-next-ci
branch
from
1e3d31b
to
e315c13
Compare
alanfx
force-pushed
the
release-next
branch
from
5a5a1a6
to
d8618d5
Compare
alanfx
force-pushed
the
release-next-ci
branch
from
e315c13
to
6a1b9bc
Compare
alanfx
force-pushed
the
release-next
branch
from
d8618d5
to
86b1324
Compare
alanfx
force-pushed
the
release-next-ci
branch
from
6a1b9bc
to
4416490
Compare
|
@alanfx: The following tests failed, say
Full PR test history. Your PR dashboard. 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. |
alanfx
force-pushed
the
release-next
branch
from
86b1324
to
683b84b
Compare
alanfx
force-pushed
the
release-next-ci
branch
from
4416490
to
8550651
Compare
|
/close |
ReToCode
pushed a commit
to ReToCode/eventing-kafka
that referenced
this pull request
Jan 3, 2023
bumping knative.dev/eventing 1725902...b20c96b: > b20c96b sinkbing implement bindable (# 4794) > 8d51418 Bump golang linter version and timeout (# 4808) > f882ff0 Add availability rate to upgrade test report (# 4555) > a6635bb Patch HPA eventing-webhook min replicas (# 4811) > d46c1d0 It is already 2021 (# 4809) > fb8fbf7 Adding new source conformance testcase for CRD RBAC (# 4787) bumping knative.dev/pkg 0d31134...ca02ef7: > ca02ef7 Genreconciler properly generates reconciler for Resources with Status (# 2004) Signed-off-by: Knative Automation <automation@knative.team>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.