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

(e2e) Reduce Consistently time for catalogsource_ready metrics check #2739

Conversation

anik120
Copy link
Contributor

@anik120 anik120 commented Apr 13, 2022

This test was checking for the catalogsource_ready metrics being emitted
with a particular value, consistently for a period of time. Consistently
blocks for the duration of time mentioned (previously 3m). Unfortunately,
there is no way to write an Eventually that starts polling after an
interval, which could have been the non-blocking alternatve to using
Consistently to perform the same check.

This PR reduces the period of time the test is blocked Consistently to
1m, to reduce the test package's overall runtime.

Ref:
https://onsi.github.io/gomega/#eventually
https://onsi.github.io/gomega/#consistently

Description of the change:

Motivation for the change:

Reviewer Checklist

  • Implementation matches the proposed design, or proposal is updated to match implementation
  • Sufficient unit test coverage
  • Sufficient end-to-end test coverage
  • Docs updated or added to /doc
  • Commit messages sensible and descriptive
  • Tests marked as [FLAKE] are truly flaky
  • Tests that remove the [FLAKE] tag are no longer flaky

@perdasilva
Copy link
Collaborator

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 13, 2022
Copy link
Contributor

@timflannagan timflannagan left a comment

Choose a reason for hiding this comment

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

Thanks - holding as this PR still needs to be rebased. Feel free to remove the hold once this PR has been updated, and the required checks are passing.

/hold

@openshift-ci openshift-ci bot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Apr 27, 2022
This test was checking for the catalogsource_ready metrics being emitted
with a particular value, consistently for a period of time. `Consistently`
blocks for the duration of time mentioned (previously 3m). Unfortunately,
there is no way to write an `Eventually` that starts polling after an
interval, which could have been the non-blocking alternatve to using
Consistently to perform the same check.

This PR reduces the period of time the test is blocked Consistently to
1m, to reduce the test package's overall runtime.

Ref:
https://onsi.github.io/gomega/#eventually
https://onsi.github.io/gomega/#consistently
Signed-off-by: Anik Bhattacharjee <anikbhattacharya93@gmail.com>
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Apr 28, 2022
@anik120
Copy link
Contributor Author

anik120 commented Apr 28, 2022

/hold cancel
@timflannagan rebased the PR, should be good to go.

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 28, 2022
@openshift-ci
Copy link

openshift-ci bot commented Apr 28, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: anik120, timflannagan

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

@timflannagan
Copy link
Contributor

oh weird: it looks like approval-acts-as-lgtm isn't enabled for this repository sadly.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 28, 2022
@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit 210b834 into operator-framework:master Apr 28, 2022
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. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants