-
Notifications
You must be signed in to change notification settings - Fork 22
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
Do not use the now removed CapacityThresholds in the tests and the utility methods. #379
Do not use the now removed CapacityThresholds in the tests and the utility methods. #379
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #379 +/- ##
=======================================
Coverage 77.98% 77.98%
=======================================
Files 47 47
Lines 1958 1958
=======================================
Hits 1527 1527
Misses 373 373
Partials 58 58 |
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.
👍
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.
LGTM
…onfig-capacity-thresholds
This can now be merged to master.
Quality Gate passedIssues Measures |
Since the CI jobs seem to be stuck (even though the GitHub Actions outage that was going on in the recent hours seems to have been resolved), I will just close this PR and open a new one from the same branch 🤞🏼 |
This has been superseded by #389.
This updates the tests to not use the
CapacityThresholds
in theToolchainConfig
, because those fields are being removed in the associatedapi
PR (codeready-toolchain/api#411).Additionally, test utility methods for the
CapacityThresholds
are also removed.See https://issues.redhat.com/browse/KUBESAW-36.
Associated PRs:
- host-operator: codeready-toolchain/host-operator#1000
- toolchain-e2e: codeready-toolchain/toolchain-e2e#935
- api: codeready-toolchain/api#411