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

Remove UpdatedContext function from context #4322

Closed
wants to merge 1 commit into from
Closed

Remove UpdatedContext function from context #4322

wants to merge 1 commit into from

Conversation

dharmit
Copy link
Member

@dharmit dharmit commented Dec 21, 2020

What type of PR is this?
/kind cleanup
/kind code-refactoring

What does this PR do / why we need it:
Removing the function since what it does seems to be already present in
the calling blocks of code.

Which issue(s) this PR fixes:

Fixes NA
Part of #4298

PR acceptance criteria:

How to test changes / Special notes to the reviewer:
Tests should pass

Removing the function since what it does seems to be already present in
the calling blocks of code.
@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dharmit

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

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. Required by Prow. label Dec 21, 2020
@dharmit
Copy link
Member Author

dharmit commented Dec 21, 2020

Commands tested locally:

  1. odo create nodejs --s2i --now
  2. odo create nodejs --s2i --now -o json

Both of the above odo create commands succeeded while testing this change locally. So we just need the CI to be green.

cc @mohammedzee1000 (since you added this code as a part of #1668.)

@girishramnani
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. Required by Prow. label Dec 31, 2020
@openshift-bot
Copy link

/retest

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

6 similar comments
@openshift-bot
Copy link

/retest

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

@openshift-bot
Copy link

/retest

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

@openshift-bot
Copy link

/retest

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

@openshift-bot
Copy link

/retest

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

@openshift-bot
Copy link

/retest

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

@openshift-bot
Copy link

/retest

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

@dharmit
Copy link
Member Author

dharmit commented Jan 1, 2021

All CI failures seem to be attributed to the same failure:

 • Failure [1.960 seconds]
odo component command tests
/go/src/github.com/openshift/odo/tests/integration/cmd_cmp_test.go:13
  Creating component
  /go/src/github.com/openshift/odo/tests/integration/component.go:49
    should describe not pushed component when it is created with json output [It]
    /go/src/github.com/openshift/odo/tests/integration/component.go:258
    Expected
      
        <string>: {
          "metadata": {
            "creationTimestamp": null
          },
          "spec": {
            "ports": [
              "8080/TCP"
            ]
          },
          "status": {
            "state": "Not Pushed"
          }
        }
    to match JSON of
        <string>: {
          "apiVersion": "odo.dev/v1alpha1",
          "kind": "Component",
          "metadata": {
            "creationTimestamp": null,
            "name": "cmp-git",
            "namespace": "tfordpsthq"
          },
          "spec": {
            "app": "testing",
            "ports": [
              "8080/TCP"
            ],
            "source": "./",
            "sourceType": "local",
            "type": "nodejs"
          },
          "status": {
            "state": "Not Pushed"
          }
        }
    /go/src/github.com/openshift/odo/tests/integration/component.go:264 

Will hold this PR and investigate the cause.

/hold

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. Required by Prow. label Jan 1, 2021
@openshift-ci
Copy link

openshift-ci bot commented Jan 1, 2021

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

Test name Commit Details Rerun command
ci/prow/v4.6-integration-e2e 00bfa66 link /test v4.6-integration-e2e

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.

@dharmit
Copy link
Member Author

dharmit commented Jan 7, 2021

Closing since the tests helped figure that there's a legit use of the function I'm trying to remove in this PR.

/close

@openshift-ci-robot
Copy link
Collaborator

@dharmit: Closed this PR.

In response to this:

Closing since the tests helped figure that there's a legit use of the function I'm trying to remove in this PR.

/close

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.

@dharmit dharmit deleted the remove-updated-context-function branch January 7, 2021 03:12
@rm3l rm3l added the area/refactoring Issues or PRs related to code refactoring label Jun 16, 2023
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. Required by Prow. area/refactoring Issues or PRs related to code refactoring do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. Required by Prow. lgtm Indicates that a PR is ready to be merged. Required by Prow.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants