-
Notifications
You must be signed in to change notification settings - Fork 242
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
[YUNIKORN-2153]Optimize Placement of predicateCheckResult for Better Maintainability #1011
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1011 +/- ##
==========================================
+ Coverage 82.48% 82.65% +0.17%
==========================================
Files 97 98 +1
Lines 15627 15645 +18
==========================================
+ Hits 12890 12932 +42
+ Misses 2457 2438 -19
+ Partials 280 275 -5 ☔ View full report in Codecov by Sentry. |
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.
A small missing function:
preemption_test.go#allocForScore
should be moved topredicates_test.go
Good catch, thanks! |
Run "make lint" locally before you push to see linter issues. |
Sorry, the current golangci-lint tool version is 1.57.2. I am not sure why it consumes my laptop huge memory usage(macos/darwin/arm64) and is never completed locally. I am trying to bump version locally and verified |
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.
+1 LGTM
What is this PR for?
Create predicate.go to encapsulate the declaration and implementation of
predicateCheckResult
, improves code organization by centralizing predicate-related logic, enhancing maintainability and readability.What type of PR is it?
Todos
What is the Jira issue?
https://issues.apache.org/jira/projects/YUNIKORN/issues/YUNIKORN-2153
How should this be tested?
2.1 Create cluster with kind and install yunikorn
2.2 Create pods with low priority but request a lot of resources
2.3 Create a pod with higher priority
2.4 Some of pods created at 2.2 are eviction and pod in 2.3 can be scheduled to k8s cluster
Screenshots (if appropriate)
Questions: