-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Add aws-serial job for MCO #13435
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
Add aws-serial job for MCO #13435
Conversation
|
/approve |
|
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 |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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: falseto 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.
|
/lgtm the correct tests ran |
|
[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 DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@fabianvf: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
@fabianvf: Updated the following 3 configmaps:
DetailsIn 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. |
No description provided.