-
Notifications
You must be signed in to change notification settings - Fork 544
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
Bug 1762769: Prioritize APIs from same CatSrc #1080
Bug 1762769: Prioritize APIs from same CatSrc #1080
Conversation
@awgreene: This pull request references Bugzilla bug 1762769, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
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. |
75e878a
to
81caff4
Compare
Where's the Definition of Done checklist in your PR description? 😉 |
Problem: When OLM installs an operator that requires dependencies that are provided via multiple operators in different CatalogSources, the API is pulled from any of the CatalogSources that provide the API. Solution: This commit introduces a change so that OLM will generate a list of operators that depend on the API, randomly select one of their sources, and prioritize checking in that CatalogSource for the API prior to checking the remaining CatalogSource for the API.
81caff4
to
b49bee6
Compare
@awgreene: This pull request references Bugzilla bug 1762769, which is valid. In response to this:
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. |
2 similar comments
@awgreene: This pull request references Bugzilla bug 1762769, which is valid. In response to this:
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. |
@awgreene: This pull request references Bugzilla bug 1762769, which is valid. In response to this:
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. |
Added! The PR updates functionality to match behavior defined in dependency-resolution.md |
/lgtm great work! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: awgreene, ecordell 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 |
@awgreene: This pull request references Bugzilla bug 1762769, which is valid. In response to this:
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. |
/retest |
3 similar comments
/retest |
/retest |
/retest |
/retest
…On Sat, Oct 19, 2019 at 9:38 AM OpenShift CI Robot ***@***.***> wrote:
@awgreene <https://github.com/awgreene>: The following test *failed*, say
/retest to rerun them all:
Test name Commit Details Rerun command
ci/prow/e2e-aws-olm b49bee6
<b49bee6>
link
<https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/operator-framework_operator-lifecycle-manager/1080/pull-ci-operator-framework-operator-lifecycle-manager-master-e2e-aws-olm/3168> /test
e2e-aws-olm
Full PR test history
<https://prow.svc.ci.openshift.org/pr-history?org=operator-framework&repo=operator-lifecycle-manager&pr=1080>.
Your PR dashboard
<https://prow.svc.ci.openshift.org/pr?query=is:pr+state:open+author:awgreene>.
Please help us cut down on flakes by linking to
<https://github.com/kubernetes/community/blob/master/contributors/devel/flaky-tests.md#filing-issues-for-flaky-tests>
an open issue
<https://github.com/operator-framework/operator-lifecycle-manager/issues?q=is:issue+is:open>
when you hit one in your PR.
Instructions for interacting with me using PR comments are available here
<https://git.k8s.io/community/contributors/guide/pull-requests.md>. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
<https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:>
repository. I understand the commands that are listed here
<https://go.k8s.io/bot-commands>.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#1080?email_source=notifications&email_token=AAAOFR3MC5Y45PFS3DFYBI3QPMEVTA5CNFSM4JB5GFR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBXP2ZQ#issuecomment-544144742>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAOFR4ABGU4LKEXXBGQ7XTQPMEVTANCNFSM4JB5GFRQ>
.
|
/retest |
1 similar comment
/retest |
/retest |
3 similar comments
/retest |
/retest |
/retest |
@awgreene: All pull requests linked via external trackers have merged. Bugzilla bug 1762769 has been moved to the MODIFIED state. In response to this:
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. |
/cherry-pick release-4.2 |
@ecordell: #1080 failed to apply on top of branch "release-4.2":
In response to this:
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. |
require.NoError(t, err) | ||
|
||
// Create duplicates of the CatalogSource | ||
for i := 0; i < 10; i++ { |
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.
@awgreene Any idea on why you settled on 10 duplicates when you were fixing this bug? Mainly curious before I attempt to make any performance improvements for this individual test case without realizing the full context.
Problem: When OLM installs an operator that requires dependencies that
are provided via multiple operators in different CatalogSources, the API
is pulled from any of the CatalogSources that provide the API.
Solution: This commit introduces a change so that OLM will generate a
list of operators that depend on the API, randomly select one of their
sources, and prioritize checking in that CatalogSource for the API prior
to checking the remaining CatalogSource for the API.
Reviewer Checklist
/docs
Fixes #1076