-
Notifications
You must be signed in to change notification settings - Fork 592
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
do not hardcode the URI, use ref instead #4278
do not hardcode the URI, use ref instead #4278
Conversation
2e7cfe3
to
f9ae776
Compare
Codecov Report
@@ Coverage Diff @@
## master #4278 +/- ##
=======================================
Coverage 80.25% 80.25%
=======================================
Files 287 287
Lines 7887 7887
=======================================
Hits 6330 6330
Misses 1174 1174
Partials 383 383 Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like using rhe ref!
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: matzew, vaikas 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 |
And then.
|
/test pull-knative-eventing-integration-tests |
* Print "Fetching trace ..." at DEBUG level because we already print another message "Exporting trace into /file/path/step-XXXX.json" at INFO level which is sufficient. * Print "Duplicate events: event #XXXX received X times, but should be received only once" at INFO level to get rid of the stacktrace that is printed at WARN level. This stack trace is really noisy and not useful at all. And with tens to hundreds of duplicate events it makes the logs really long. This will reduce the log in the following way for each duplicate event: Before: ``` 2023-01-19T09:54:40.013-0500 WARN prober/verify.go:99 Duplicate events: event #4278 received 2 times, but should be received only once knative.dev/eventing/test/upgrade/prober.(*prober).Verify /tmp/gopath-ZSUHshgs6a/src/github.com/openshift-knative/serverless-operator/vendor/knative.dev/eventing/test/upgrade/prober/verify.go:99 knative.dev/eventing/test/upgrade/prober.(*probeRunner).Verify /tmp/gopath-ZSUHshgs6a/src/github.com/openshift-knative/serverless-operator/vendor/knative.dev/eventing/test/upgrade/prober/prober.go:74 knative.dev/eventing/test/upgrade/prober.NewContinualVerification.func2 /tmp/gopath-ZSUHshgs6a/src/github.com/openshift-knative/serverless-operator/vendor/knative.dev/eventing/test/upgrade/prober/continual.go:56 knative.dev/pkg/test/upgrade.NewBackgroundVerification.func1.1 /tmp/gopath-ZSUHshgs6a/src/github.com/openshift-knative/serverless-operator/vendor/knative.dev/pkg/test/upgrade/functions.go:65 knative.dev/pkg/test/upgrade.handleStopEvent /tmp/gopath-ZSUHshgs6a/src/github.com/openshift-knative/serverless-operator/vendor/knative.dev/pkg/test/upgrade/functions.go:126 knative.dev/pkg/test/upgrade.WaitForStopEvent /tmp/gopath-ZSUHshgs6a/src/github.com/openshift-knative/serverless-operator/vendor/knative.dev/pkg/test/upgrade/functions.go:94 knative.dev/pkg/test/upgrade.NewBackgroundVerification.func1 /tmp/gopath-ZSUHshgs6a/src/github.com/openshift-knative/serverless-operator/vendor/knative.dev/pkg/test/upgrade/functions.go:62 knative.dev/pkg/test/upgrade.(*suiteExecution).startContinualTests.func1.2 /tmp/gopath-ZSUHshgs6a/src/github.com/openshift-knative/serverless-operator/vendor/knative.dev/pkg/test/upgrade/steps.go:81 2023-01-19T09:54:40.013-0500 INFO prober/verify.go:135 Fetching trace for Step event #4278 2023-01-19T09:54:42.593-0500 INFO prober/verify.go:168 Exporting trace into /home/jenkins/workspace/functional_tests/stream1_27/rolling-upgrade-1.27/artifacts/build-18/traces/events/step-4278.json ``` After: ``` 2023-01-19T09:54:40.013-0500 INFO prober/verify.go:99 WARNING: Duplicate: event #4278 received 2 times, but should be received only once 2023-01-19T09:54:42.593-0500 INFO prober/verify.go:168 Exporting trace into /home/jenkins/workspace/functional_tests/stream1_27/rolling-upgrade-1.27/artifacts/build-18/traces/events/step-4278.json ``` Fixes # <!-- Please include the 'why' behind your changes if no issue exists --> ## Proposed Changes <!-- Please categorize your changes: - :gift: Add new feature - :bug: Fix bug - :broom: Update or clean up current behavior - :wastebasket: Remove feature or internal logic --> - - - ### Pre-review Checklist <!-- If these boxes are not checked, you will be asked to complete these requirements or explain why they do not apply to your PR. --> - [ ] **At least 80% unit test coverage** - [ ] **E2E tests** for any new behavior - [ ] **Docs PR** for any user-facing impact - [ ] **Spec PR** for any new API feature - [ ] **Conformance test** for any change to the spec **Release Note** <!-- :page_facing_up: If this change has user-visible impact, write a release note in the block below. Include the string "action required" if additional action is required of users switching to the new release, for example in case of a breaking change. Write as if you are speaking to users, not other Knative contributors. If this change has no user-visible impact, no release note is needed. --> ```release-note ``` **Docs** <!-- :book: If this change has user-visible impact, link to an issue or PR in https://github.com/knative/docs. -->
Proposed Changes
Release Note
Docs