-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Demote HPA tests from release-blocking #81537
Demote HPA tests from release-blocking #81537
Conversation
Add a Feature:HPA tag to these tests so they're not picked up by the release-blocking job that focuses on [Serial] tests (but excludes [Feature:.*] tests) They take a combined 70 minutes on average. If they really need to be in release-blocking as implemented, we should consider a separate job to focus just on this feature.
While I did a search to see how the |
/hold |
/retest |
/assign @mwielgus |
@spiffxp I see the problem. We would rather move to a separate job than get off blocking tests completely. If possible, please keep this PR on hold while we are working on this. cc: @josephburnett |
I described how to do this in #81491 (comment) Can we accept a blip in coverage and allow this to merge so the new job can be written to focus on |
@spiffxp sure. I'll start on the Feature:HPA job tomorrow. |
/lgtm |
/hold cancel |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: josephburnett, spiffxp 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 |
/lgtm |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Add a
[Feature:HPA]
tag to these tests so they're not picked up by the release-blocking job that focuses on[Serial]
tests (but excludes[Feature:.*]
tests)They take a combined 70 minutes on average. If they really need to be in release-blocking as implemented, we should consider a separate job to focus just on this feature.
Which issue(s) this PR fixes:
Addresses part of #81491
Does this PR introduce a user-facing change?:
/priority important-soon