Skip to content

chore(revision): Remove unwanted log message in test#267

Merged
knative-prow-robot merged 2 commits intoknative:masterfrom
rhuss:pr/test-fix
Jul 22, 2019
Merged

chore(revision): Remove unwanted log message in test#267
knative-prow-robot merged 2 commits intoknative:masterfrom
rhuss:pr/test-fix

Conversation

@rhuss
Copy link
Copy Markdown
Contributor

@rhuss rhuss commented Jul 16, 2019

This showed up in the test run as single log message so removing it

This showed up in the test run as single log message so I removed that.
@googlebot googlebot added the cla: yes Indicates the PR's author has signed the CLA. label Jul 16, 2019
@knative-prow-robot knative-prow-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jul 16, 2019
@rhuss
Copy link
Copy Markdown
Contributor Author

rhuss commented Jul 16, 2019

/retest

TypeMeta: metav1.TypeMeta{
Kind: "Revision",
APIVersion: "knative.dev/v1alpha1",
APIVersion: "serving.knative.dev/v1alpha1",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The change seems to be at odd with the title...

Copy link
Copy Markdown
Contributor Author

@rhuss rhuss Jul 17, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The test is broken, as it does not break because of the wrong coordinates (in fact it the api group is serving.knative.dev/v1alpha1, it's just not checked in this test, so it's meaningless anyway.

Happy to revert back to the wrong coordinates though.

Copy link
Copy Markdown
Contributor

@maximilien maximilien left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you change title to reflect change and 'll approve and lgtm

@rhuss
Copy link
Copy Markdown
Contributor Author

rhuss commented Jul 17, 2019

Reverted the unrelated fix, and will send in a new PR with fixes for all test with a broken API group

@rhuss rhuss changed the title chore(revision): Remove bogus log message chore(revision): Remove unwanted log message in test Jul 17, 2019
@rhuss
Copy link
Copy Markdown
Contributor Author

rhuss commented Jul 17, 2019

/retest

1 similar comment
@rhuss
Copy link
Copy Markdown
Contributor Author

rhuss commented Jul 18, 2019

/retest

@rhuss
Copy link
Copy Markdown
Contributor Author

rhuss commented Jul 18, 2019

/retest

The flaky test should be fixed with #271 .

@mattmoor mattmoor removed their request for review July 18, 2019 14:00
@rhuss
Copy link
Copy Markdown
Contributor Author

rhuss commented Jul 18, 2019

/retest

@rhuss
Copy link
Copy Markdown
Contributor Author

rhuss commented Jul 18, 2019

Guess we have to wait until #271 is merged to get the test green again.

@cppforlife
Copy link
Copy Markdown

/retest
/lgtm
/approve

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 22, 2019
@knative-prow-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cppforlife, navidshaikh, rhuss

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:

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

@maximilien
Copy link
Copy Markdown
Contributor

/lgtm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants