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

Imagestream error on experimental mode #3314

Conversation

amitkrout
Copy link
Contributor

What type of PR is this?
missing integration test

What does does this PR do / why we need it:
Adding integration test coverage for imagestream error on experimental mode
Which issue(s) this PR fixes:

Fixes - missing integration test of #3265

How to test changes / Special notes to the reviewer:
make test-cmd-devfile-create

@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign amitkrout
You can assign the PR to them by writing /assign @amitkrout in a comment when ready.

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

@amitkrout amitkrout added the area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering label Jun 6, 2020
@amitkrout amitkrout force-pushed the imagestreamErrorOnExperimentalMode branch from 814c08f to 16c4c7c Compare June 8, 2020 10:55
@@ -58,6 +58,14 @@ var _ = Describe("odo devfile create command tests", func() {
})
})

Context("When executing odo create with incorrect devfile component", func() {
Copy link
Contributor

Choose a reason for hiding this comment

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

@amitkrout Does incorrect devfile and invalid differs? I think we do have spec for the same https://github.com/openshift/odo/pull/3314/files#diff-5291a6a42f2148d4c3e48ea4b73cff23R136 . Correct me if I am missing something.

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 original pr #3265 its clearly mentioned in the pr description that the component mane is invalid not incorrect. so I replaced invalid with incorrect to be in more sync with the original pr.

@prietyc123 Does it make sense now ?

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes, that's true we have invalid component name but what I mean is the spec that you are adding is duplicate of line no 136 https://github.com/openshift/odo/pull/3314/files#diff-5291a6a42f2148d4c3e48ea4b73cff23R136 .

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ahhh...Got it. You know its the Monday effect hahaha...

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good catch !!!

@openshift-ci-robot
Copy link
Collaborator

@amitkrout: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/v4.3-integration-e2e b26a2c0 link /test v4.3-integration-e2e
ci/prow/v4.4-integration-e2e b26a2c0 link /test v4.4-integration-e2e
ci/prow/v4.2-integration-e2e b26a2c0 link /test v4.2-integration-e2e
ci/prow/v4.5-integration-e2e b26a2c0 link /test v4.5-integration-e2e

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.

@girishramnani
Copy link
Contributor

as per discussion, added changes of this PR on #3322

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants