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

OCM-11127 | ci: fix id:73753,55883,75927 #2458

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

aaraj7
Copy link
Contributor

@aaraj7 aaraj7 commented Sep 13, 2024

No description provided.

@yingzhanredhat
Copy link
Contributor

/lgtm

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

openshift-ci bot commented Sep 13, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: aaraj7, yingzhanredhat
Once this PR has been reviewed and has the lgtm label, please assign ciaranroche for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found 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

Copy link

codecov bot commented Sep 13, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 29.35%. Comparing base (3763187) to head (395ecb0).
Report is 2 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #2458   +/-   ##
=======================================
  Coverage   29.35%   29.35%           
=======================================
  Files         161      161           
  Lines       22364    22364           
=======================================
  Hits         6566     6566           
  Misses      15253    15253           
  Partials      545      545           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@@ -3530,6 +3530,7 @@ var _ = Describe("Sts cluster creation supplemental testing",
testOperatorRolePrefix := common.GenerateRandomName("opp75927", 2)
flags, err := profilehandler.GenerateClusterCreateFlags(customProfile, rosaClient)
Expect(err).ToNot(HaveOccurred())
rolePrefix = flags[16]
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this arbitrary ? SHouldn't you use GetFlagValue ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The next test case uses same method, so I became just consistent, If you will tell I will change, wdyt?

Copy link
Contributor

Choose a reason for hiding this comment

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

I would rather use some discovery than using hardcoded index which may change quite easily

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Okay will change it Thanks

@@ -392,8 +392,6 @@ var _ = Describe("Cluster Upgrade testing",
By("Check upgrade state")
err = WaitForUpgradeToState(upgradeService, clusterID, con.Scheduled, 4)
Expect(err).To(BeNil())
err = WaitForUpgradeToState(upgradeService, clusterID, con.Started, 70)
Copy link
Contributor

Choose a reason for hiding this comment

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

We don't wait for upgrade started anymore ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

If we will wait, the upgrade started will never be cancelled/deleted for next test cases.

Copy link
Contributor

Choose a reason for hiding this comment

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

In the test case I see Check the upgrade is finished successfully
So we should add a step to wait for the upgrade

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Okay will try to mould the test case same

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 16, 2024
@aaraj7 aaraj7 changed the title OCM-11127 | ci: fix id:73753,67414,55883,75927 OCM-11127 | ci: fix id:73753,55883,75927 Sep 17, 2024
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Sep 19, 2024
Copy link
Contributor

openshift-ci bot commented Sep 19, 2024

New changes are detected. LGTM label has been removed.

@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 19, 2024
Copy link
Contributor

openshift-ci bot commented Sep 19, 2024

@aaraj7: all tests passed!

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants