Skip to content

Conversation

@fabianvf
Copy link
Member

@fabianvf fabianvf commented Nov 5, 2020

No description provided.

@yuqi-zhang
Copy link
Contributor

/approve

@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 5, 2020
@deads2k
Copy link
Contributor

deads2k commented Nov 5, 2020

going to make sure the e2e-serial tests at least start running in the rehearse to know we got the right things.

secretName: result-aggregator
trigger: (?m)^/test( | .* )e2e-aws-proxy,?($|\s.*)
- agent: kubernetes
always_run: true
Copy link
Member

Choose a reason for hiding this comment

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

How often has the MCO broken serial tests? If this is a one-off, I'd consider always_run: false to save some CI-volume cost. This property is one that you can hand-edit in this file; it is not fed from the config YAML.

I'd also consider optional: true, to allow the MCO to merge PRs where serial tests were failing. But that's mostly to keep their throughput up if serial starts flaking out for some non-MCO reason, and if they only call in the serial tests occasionally (with an always_run: false change), requiring serial to pass or be explicitly /overriden seems reasonable too.

Copy link
Contributor

Choose a reason for hiding this comment

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

How often has the MCO broken serial tests? If this is a one-off, I'd consider always_run: false to save some CI-volume cost. This property is one that you can hand-edit in this file; it is not fed from the config YAML.

Everyone will say they break it infrequently. I think it's low enough in the stack to warrant it and there's an explicit scaling test where the machine-api often suspects the MCO. It came up multiple times in 4.6.

@deads2k
Copy link
Contributor

deads2k commented Nov 5, 2020

/lgtm

the correct tests ran

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

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k, fabianvf, yuqi-zhang

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

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

Test name Commit Details Rerun command
ci/rehearse/openshift/machine-config-operator/master/e2e-aws-serial b462a16 link /test pj-rehearse
ci/prow/pj-rehearse b462a16 link /test pj-rehearse

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 openshift-merge-robot merged commit 4ea8ecf into openshift:master Nov 5, 2020
@openshift-ci-robot
Copy link
Contributor

@fabianvf: Updated the following 3 configmaps:

  • job-config-master configmap in namespace ci at cluster api.ci using the following files:
    • key openshift-machine-config-operator-master-presubmits.yaml using file ci-operator/jobs/openshift/machine-config-operator/openshift-machine-config-operator-master-presubmits.yaml
  • job-config-master configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-machine-config-operator-master-presubmits.yaml using file ci-operator/jobs/openshift/machine-config-operator/openshift-machine-config-operator-master-presubmits.yaml
  • ci-operator-master-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-machine-config-operator-master.yaml using file ci-operator/config/openshift/machine-config-operator/openshift-machine-config-operator-master.yaml
Details

In response to this:

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

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