Skip to content

Conversation

@adambkaplan
Copy link
Contributor

Cleaned up from #24111 - should get 4.1.z tests back to green.

Update build, cmd, and integration tests to use centos/ruby-25-centos7 image
* Skip test-util suite in test-cmd
* Remove named ports in cmd and unit tests
@openshift-ci-robot
Copy link

@adambkaplan: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

[4.1.z] Fix origin tests

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-robot openshift-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Nov 20, 2019
@adambkaplan adambkaplan changed the title [4.1.z] Fix origin tests Bug 1769951: [4.1.z] Fix origin tests Nov 20, 2019
@openshift-ci-robot
Copy link

@adambkaplan: This pull request references Bugzilla bug 1769951, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Bug 1769951: [4.1.z] Fix origin tests

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-robot openshift-ci-robot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Nov 20, 2019
@adambkaplan
Copy link
Contributor Author

/assign @bparees

/cc @eparis

Makefile Outdated
# make test-cmd
test-cmd: build
hack/test-util.sh
# hack/test-util.sh
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 intentional? If so, what about deleting the line instead?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes - this is intentional. TBH I did not have time to dig into why these tests were failing - it seemed that the suite itself is a "test of the tests" and has dependencies which no longer exist in the container running the tests.

@eparis
Copy link
Member

eparis commented Nov 20, 2019

/lgtm
/approve

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Nov 20, 2019
@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adambkaplan, eparis

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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. label Nov 20, 2019
@openshift-bot
Copy link
Contributor

/retest

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

@eparis eparis added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Nov 20, 2019
@eparis
Copy link
Member

eparis commented Nov 20, 2019

I'm applying cherrypick approved, hopefully it will mean tomorrow when 4.1 opens stuff can actually merge.

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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants