Skip to content

ci-operator/config/openshift/telemeter: Generic e2e for 4.6+ #11459

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.

Sign up for GitHub

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

Jump to bottom
Closed
wking wants to merge 1 commit into from
Closed

ci-operator/config/openshift/telemeter: Generic e2e for 4.6+ #11459

wking wants to merge 1 commit into from

Conversation

@wking
Copy link
Member

@wking wking commented Aug 31, 2020

Following the pattern from e7bb102 (#10152), this commit is using platform-agnostic names. The role of platform-agnostic tests is discussed here. The choice of a GCP implementation for the now-agnostic tests is because we currently have free GCP capacity, while AWS is maxed out.

I've left the benchmark test on AWS, because I'm not sure what that's about. It might be AWS-specific.

@wking
ci-operator/config/openshift/telemeter: Generic e2e for 4.6+
6105b1d 
Following the pattern from e7bb102
(ci-operator/config/openshift/cluster-version-operator: Generic
e2e-gcp -> e2e for 4.4+, 2020-07-09, openshift#10152), this commit is using
platform-agnostic names.  The role of platform-agnostic tests is
discussed in ci-operator/platform-balance.  The choice of a GCP
implementation for the now-agnostic tests is because we currently have
free GCP capacity, while AWS is maxed out.

I've left the benchmark test on AWS, because I'm not sure what that's
about.  It might be AWS-specific.

Generated by manually changing `ci-operator/config/...`, running:

  $ make update
@wking wking force-pushed the platform-agnostic-telemeter branch from d2a358d to 6105b1d Compare August 31, 2020 20:55
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Aug 31, 2020

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

The full list of commands accepted by this bot can be found 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

@maorfr
Copy link
Member

maorfr commented Sep 23, 2020

/uncc

@openshift-ci-robot openshift-ci-robot removed the request for review from maorfr September 23, 2020 07:01
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Oct 9, 2020

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

Test name Commit Details Rerun command
ci/rehearse/openshift/telemeter/release-4.7/e2e-upgrade 6105b1d link /test pj-rehearse
ci/rehearse/openshift/telemeter/release-4.7/e2e 6105b1d link /test pj-rehearse
ci/prow/pj-rehearse 6105b1d link /test pj-rehearse
ci/prow/ci-testgrid-allow-list 6105b1d link /test ci-testgrid-allow-list
ci/prow/yamllint 6105b1d link /test yamllint
ci/prow/boskos-config 6105b1d link /test boskos-config

Full PR test history. Your PR dashboard.

Details

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

openshift-merge-robot commented Nov 10, 2020

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

Test name Commit Details Rerun command
ci/prow/release-config 6105b1d link /test release-config
ci/prow/boskos-config-generation 6105b1d link /test boskos-config-generation
ci/prow/secret-generator-config-valid 6105b1d link /test secret-generator-config-valid
ci/prow/deprecate-templates 6105b1d link /test deprecate-templates

Full PR test history. Your PR dashboard.

Details

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

openshift-ci bot commented Feb 26, 2021

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

Test name Commit Details Rerun command
ci/prow/ci-secret-generator-config 6105b1d link /test ci-secret-generator-config
ci/prow/ci-secret-bootstrap-config-validation 6105b1d link /test ci-secret-bootstrap-config-validation

Full PR test history. Your PR dashboard.

Details

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

openshift-bot commented May 27, 2021

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 27, 2021
@openshift-bot
Copy link
Contributor

openshift-bot commented Jun 26, 2021

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 26, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 26, 2021

@wking: PR needs rebase.

Details

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 the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 26, 2021
@openshift-bot
Copy link
Contributor

openshift-bot commented Jul 27, 2021

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci bot closed this Jul 27, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 27, 2021

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@aditya-konarde aditya-konarde Awaiting requested review from aditya-konarde

Assignees

No one assigned

Labels

lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@wking @openshift-ci-robot @maorfr @openshift-merge-robot @openshift-bot