-
Notifications
You must be signed in to change notification settings - Fork 136
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-2685] Use the newer WaitForCondition() in shim test #858
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #858 +/- ##
==========================================
+ Coverage 67.16% 67.30% +0.13%
==========================================
Files 70 70
Lines 7639 7631 -8
==========================================
+ Hits 5131 5136 +5
+ Misses 2289 2277 -12
+ Partials 219 218 -1 ☔ View full report in Codecov by Sentry. |
cc @wilfred-s @craigcondit do we ever import stuff from the core directly? We do it for the deadlock detection, but apart from that, I haven't seen this practice anywhere. |
@mean-world Sorry I wasn't aware that there is a similar function in shim's utils. For me, I would vote to align the implementation of WaitForCondition(), but keep two separate function in shim and core. |
there are use case already. yunikorn-k8shim/pkg/cache/task_test.go Line 203 in 24efbed
The core and k8shim are different repo, so it will be a issue in aligning the version, but reusing the utils methods is always good to me. |
We shouldn't share code between core and shim. The scheduler interface is meant to be the common point. There are exceptions for some low-level functionality like locks and logging, but that's out of necessity. Tightly coupling the two projects just creates friction and makes refactoring more difficult. The other examples just given should probably be fixed to not use core code. |
that sounds good to me. Maybe we can have another jira to cleanup the usage of core code. |
We're on the same page. This PR can be closed and a new ticket should eliminate the existiting core imports where it's possible. @mean-world please create a new JIRA and close this one. |
I already create new JIRA |
What is this PR for?
shim completly use WaitForCondition function from yunikorn-core
also remove E2E test about Dao.allocation.partition based on YUNIKORN-2593
What type of PR is it?
Todos
What is the Jira issue?
https://issues.apache.org/jira/browse/YUNIKORN-2685
How should this be tested?
Screenshots (if appropriate)
Questions: