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-1677: Fix devfile registry assertion #12085

Merged
merged 1 commit into from Sep 23, 2022

Conversation

jerolimov
Copy link
Member

Fixes:
https://issues.redhat.com/browse/OCPBUGS-1677

Analysis / Root cause:
pkg/devfile/sample_test.go fails after devfile registry was updated (devfile/registry#126)

Solution Description:
Just updated the assertion.

https://issues.redhat.com/browse/OCPBUGS-1678 is about updating the code so that the test should use a mock response instead of the latest registry content OR check some specific attributes instead of comparing the full JSON response.

@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. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Sep 23, 2022
@openshift-ci-robot
Copy link
Contributor

@jerolimov: This pull request references Jira Issue OCPBUGS-1677, 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.12.0) matches configured target version for branch (4.12.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

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

In response to this:

Fixes:
https://issues.redhat.com/browse/OCPBUGS-1677

Analysis / Root cause:
pkg/devfile/sample_test.go fails after devfile registry was updated (devfile/registry#126)

Solution Description:
Just updated the assertion.

https://issues.redhat.com/browse/OCPBUGS-1678 is about updating the code so that the test should use a mock response instead of the latest registry content OR check some specific attributes instead of comparing the full JSON response.

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.

@openshift-ci openshift-ci bot added component/backend Related to backend approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Sep 23, 2022
Copy link
Member

@jhadvig jhadvig left a comment

Choose a reason for hiding this comment

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

/lgtm

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

openshift-ci bot commented Sep 23, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jerolimov, jhadvig

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

@@ -72,7 +72,7 @@ func TestGetRegistrySamples(t *testing.T) {
DisplayName: "Basic Python",
Description: "A simple Hello World application using Python",
Tags: []string{"Python"},
Icon: "https://www.python.org/static/community_logos/python-logo-generic.svg",
Icon: "https://raw.githubusercontent.com/devfile-samples/devfile-stack-icons/main/python.svg",
Copy link
Member

Choose a reason for hiding this comment

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

Should we consider relaxing some of these tests so they don't break when things change? For instance, checking if python exists, has some icon, etc, but not necessarily all of the exact values.

Let's merge this to unblock CI, but maybe as a follow up.

Copy link
Member

Choose a reason for hiding this comment

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

OK I see this is already tracked by https://issues.redhat.com/browse/OCPBUGS-1678, thanks 👍

Copy link
Member

Choose a reason for hiding this comment

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

ccing @jerolimov

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 23, 2022

@jerolimov: 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/test-infra repository. I understand the commands that are listed here.

@openshift-merge-robot openshift-merge-robot merged commit dd96b2f into openshift:master Sep 23, 2022
@openshift-ci-robot
Copy link
Contributor

@jerolimov: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-1677 has been moved to the MODIFIED state.

In response to this:

Fixes:
https://issues.redhat.com/browse/OCPBUGS-1677

Analysis / Root cause:
pkg/devfile/sample_test.go fails after devfile registry was updated (devfile/registry#126)

Solution Description:
Just updated the assertion.

https://issues.redhat.com/browse/OCPBUGS-1678 is about updating the code so that the test should use a mock response instead of the latest registry content OR check some specific attributes instead of comparing the full JSON response.

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.

@jerolimov
Copy link
Member Author

/cherry-pick release-4.11

@openshift-cherrypick-robot

@jerolimov: new pull request created: #12108

In response to this:

/cherry-pick release-4.11

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.

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. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. component/backend Related to backend jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants