Skip to content

ci-operator/step-registry/openshift/e2e/test: Add TEST_COMMAND and TEST_SUITE #9676

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

Merged

Conversation

wking
Copy link
Member

@wking wking commented Jun 16, 2020

Taking advantage of openhsift/ci-tools@62e7498d66 (openshift/ci-tools#854). This commit doesn't override the defaults yet, but a useful override would be:

TEST_COMMAND=run-upgrade
TEST_SUITE=all

This replaces test-suite.txt, which landed in a2fd8c3 (#6965), and also had no consumers.

…ST_SUITE

Taking advantage of openhsift/ci-tools@62e7498d66 (ci-operator
multi-stage: add step parameters, 2020-05-27, openshift/ci-tools#854).
This commit doesn't override the defaults yet, but a useful override
would be:

  TEST_COMMAND=run-upgrade
  TEST_SUITE=all

This replaces test-suite.txt, which landed in a2fd8c3
(step-registry: add Origin E2E test step, 2020-01-31, openshift#6965), and also
had no consumers.
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 16, 2020
@openshift-ci-robot
Copy link
Contributor

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

Test name Commit Details Rerun command
ci/rehearse/openshift/cluster-network-operator/master/e2e-vsphere 7b8e5e1 link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-vsphere 7b8e5e1 link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-azure-shared-vpc 7b8e5e1 link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-aws-shared-vpc 7b8e5e1 link /test pj-rehearse
ci/rehearse/openshift/cloud-credential-operator/master/e2e-azure 7b8e5e1 link /test pj-rehearse
ci/rehearse/openshift/cluster-network-operator/master/e2e-ovn-hybrid-step-registry 7b8e5e1 link /test pj-rehearse
ci/rehearse/openshift/cluster-network-operator/master/e2e-ovn-step-registry 7b8e5e1 link /test pj-rehearse
ci/prow/pj-rehearse 7b8e5e1 link /test pj-rehearse

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.

@bbguimaraes
Copy link
Contributor

Heh, you beat me to it by half a day: bbguimaraes@92e589e.

Thanks!

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jun 16, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bbguimaraes, wking

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-bot
Copy link
Contributor

/retest

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

@openshift-merge-robot openshift-merge-robot merged commit 7e2dd7d into openshift:master Jun 16, 2020
@openshift-ci-robot
Copy link
Contributor

@wking: Updated the following 2 configmaps:

  • step-registry configmap in namespace ci at cluster api.ci using the following files:
    • key openshift-e2e-test-commands.sh using file ci-operator/step-registry/openshift/e2e/test/openshift-e2e-test-commands.sh
    • key openshift-e2e-test-ref.yaml using file ci-operator/step-registry/openshift/e2e/test/openshift-e2e-test-ref.yaml
  • step-registry configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-e2e-test-commands.sh using file ci-operator/step-registry/openshift/e2e/test/openshift-e2e-test-commands.sh
    • key openshift-e2e-test-ref.yaml using file ci-operator/step-registry/openshift/e2e/test/openshift-e2e-test-ref.yaml

In response to this:

Taking advantage of openhsift/ci-tools@62e7498d66 (openshift/ci-tools#854). This commit doesn't override the defaults yet, but a useful override would be:

TEST_COMMAND=run-upgrade
TEST_SUITE=all

This replaces test-suite.txt, which landed in a2fd8c3 (#6965), and also had no consumers.

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.

@wking wking deleted the test-suite-step-parameter branch June 16, 2020 12:42
@@ -2,6 +2,13 @@ ref:
as: openshift-e2e-test
from: tests
commands: openshift-e2e-test-commands.sh
env:
- name: TEST_COMMAND
Copy link
Contributor

Choose a reason for hiding this comment

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

This unfortunately doesn’t solve the common “run a type of suite like upgrade and then run the normal suite”.

I would recommend not abstracting the test command into multiple steps, just accept a test command like we do in CI chunks today. I don’t think this is going to address our needs well.

Copy link
Member Author

Choose a reason for hiding this comment

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

No worries, we can still iterate ;)

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. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants