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

OCPBUGS-45029: dev-console cypress feature file test update #14685

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

The-Anton
Copy link
Member

@The-Anton The-Anton commented Jan 16, 2025

@openshift-ci openshift-ci bot added the component/dev-console Related to dev-console label Jan 16, 2025
Copy link
Contributor

openshift-ci bot commented Jan 16, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: The-Anton
Once this PR has been reviewed and has the lgtm label, please assign psrna for approval. For more information see the 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

@openshift-ci openshift-ci bot added the component/topology Related to topology label Jan 16, 2025
@The-Anton The-Anton changed the title [No-Jira] : dev-console cypress feature file test case update [No-Jira] : dev-console cypress feature file test update Jan 16, 2025
@The-Anton
Copy link
Member Author

/retest

@The-Anton
Copy link
Member Author

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@The-Anton: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

@The-Anton The-Anton changed the title [No-Jira] : dev-console cypress feature file test update OCPBUGS-45029 : dev-console cypress feature file test update Jan 17, 2025
@The-Anton
Copy link
Member Author

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@The-Anton: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

@The-Anton The-Anton changed the title OCPBUGS-45029 : dev-console cypress feature file test update OCPBUGS-45029: dev-console cypress feature file test update Jan 17, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Jan 17, 2025
@openshift-ci-robot
Copy link
Contributor

@The-Anton: This pull request references Jira Issue OCPBUGS-45029, which is invalid:

  • expected the bug to target either version "4.19." or "openshift-4.19.", but it targets "4.18.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

OCPBUGS-45031, OCPBUGS-45023, OCPBUGS-45025, OCPBUGS-45030, OCPBUGS-45029, OCPBUGS-45018, OCPBUGS-45032

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Jan 17, 2025
@The-Anton
Copy link
Member Author

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@The-Anton: This pull request references Jira Issue OCPBUGS-45029, which is invalid:

  • expected the bug to target either version "4.19." or "openshift-4.19.", but it targets "4.18.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

@The-Anton
Copy link
Member Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 17, 2025
@openshift-ci-robot
Copy link
Contributor

@The-Anton: This pull request references Jira Issue OCPBUGS-45029, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sanketpathak

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

@The-Anton
Copy link
Member Author

/retest

@openshift-ci-robot
Copy link
Contributor

@The-Anton: This pull request references Jira Issue OCPBUGS-45029, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sanketpathak

In response to this:

Fix : OCPBUGS-45031, OCPBUGS-45023, OCPBUGS-45025, OCPBUGS-45030, OCPBUGS-45029, OCPBUGS-45018, OCPBUGS-45032

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 openshift-eng/jira-lifecycle-plugin repository.

@The-Anton
Copy link
Member Author

/retest

1 similar comment
@The-Anton
Copy link
Member Author

/retest

@The-Anton
Copy link
Member Author

/test e2e-gcp-console

Copy link
Contributor

openshift-ci bot commented Jan 22, 2025

@The-Anton: 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
component/dev-console Related to dev-console component/topology Related to topology jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants