Skip to content
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

Invalid Sink URI CloudEvent test sometimes includes quotes #2166

Merged
merged 1 commit into from Mar 5, 2020
Merged

Invalid Sink URI CloudEvent test sometimes includes quotes #2166

merged 1 commit into from Mar 5, 2020

Conversation

ghost
Copy link

@ghost ghost commented Mar 5, 2020

Changes

In the logs for the latest pipeline nightly we saw a failed unit test for CloudEvents with the following message:

TestSendCloudEvent/send_a_cloud_event_with_invalid_sink_URI: cloudevent_test.go:106: I expected an error like invalid_URI: unsupported protocol scheme, but I got Post "invalid_URI": unsupported protocol scheme ""

It appears that sometimes the "invalid_URI" part of the error message will include quotes, and sometimes (like when running locally) it won't.

This PR updates the regex to allow for these quotes in the error message.

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

See the contribution guide for more details.

Double check this list of stuff that's easy to miss:

Reviewer Notes

If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.

In the logs for the latest pipeline nightly we saw a failed unit test
for CloudEvents with the following message:

```
TestSendCloudEvent/send_a_cloud_event_with_invalid_sink_URI:
cloudevent_test.go:106: I expected an error like invalid_URI:
unsupported protocol scheme, but I got Post "invalid_URI": unsupported
protocol scheme ""
```

It appears that sometimes the "invalid_URI" part of the error message
will include quotes, and sometimes (like when running locally) it won't.

This PR updates the regex to allow for these quotes in the error message.
@googlebot googlebot added the cla: yes Trying to make the CLA bot happy with ppl from different companies work on one commit label Mar 5, 2020
@tekton-robot tekton-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Mar 5, 2020
Copy link
Member

@dibyom dibyom left a comment

Choose a reason for hiding this comment

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

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 5, 2020
@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dibyom

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 5, 2020
@tekton-robot tekton-robot merged commit f5a21ee into tektoncd:master Mar 5, 2020
@ghost ghost added needs-cherry-pick Indicates a PR needs to be cherry-pick to a release branch and removed needs-cherry-pick Indicates a PR needs to be cherry-pick to a release branch labels Mar 6, 2020
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 Trying to make the CLA bot happy with ppl from different companies work on one commit 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.

3 participants