-
Notifications
You must be signed in to change notification settings - Fork 2k
adding best_effort for int gather_extra runs #71324
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
Conversation
|
Skipping CI for Draft Pull Request. |
|
[REHEARSALNOTIFIER]
Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals. Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/pj-rehearse periodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallel |
|
@sclarkso: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse periodic-ci-Azure-ARO-HCP-main-periodic-integration-e2e-parallel |
|
@sclarkso: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@sclarkso: all tests passed! Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
| LOCATION: uksouth | ||
| post: | ||
| - ref: aro-hcp-provision-aro-hcp-gather-extra | ||
| - chain: aro-hcp-provision-aro-hcp-gather-extra-best-effort |
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.
this should be a best effort in all cases where we use them IMO .
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.
I asked in the thread and was waiting for a response. If it can be for EVERY run of that test, then we can just modify the config to allow, and then add the best_effort: true to the step-registry I think, instead of adding the chain.
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.
Ahh i missed that . IMO yes we should .
|
lgtm overall . |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: raelga, sclarkso The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@raelga Per the slack discussion, I attempted this. I have not made prow changes before, so this could be the wrong direction. I added a chain file so that best_effort could be set for specific runs and not affect all runs by modifying the gather_extra step directly.