Open 7h3-3mp7y-m4n opened 1 week ago
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: 7h3-3mp7y-m4n Once this PR has been reviewed and has the lgtm label, please assign mimowo for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Welcome @7h3-3mp7y-m4n!
It looks like this is your first PR to kubernetes-sigs/kueue 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.
You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.
You can also check if kubernetes-sigs/kueue has its own contribution guidelines.
You may want to refer to our testing guide if you run into trouble with your tests not passing.
If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!
Thank you, and welcome to Kubernetes. :smiley:
Hi @7h3-3mp7y-m4n. Thanks for your PR.
I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
Name | Link |
---|---|
Latest commit | 84d415a9f278ac3b992e00de3a849c413a901556 |
Latest deploy log | https://app.netlify.com/sites/kubernetes-sigs-kueue/deploys/674721ffe9e583000850bb3a |
@mbobrovskyi: /release-note-edit must be used with a release note block.
/ok-to-test
/release-note-edit
NONE
/assign @gabesaba
There are some other log lines related to this issue:
e.g. these two, as AddOrUpdateWorkload
calls AddOrUpdateWorkloadWithoutLock
https://github.com/kubernetes-sigs/kueue/blob/2c8e7da1a23f2bc7218a2f08a2c9858a316fb053/pkg/controller/core/workload_controller.go#L602-L604
https://github.com/kubernetes-sigs/kueue/blob/2c8e7da1a23f2bc7218a2f08a2c9858a316fb053/pkg/controller/core/workload_controller.go#L744-L746
Could you track those down - there may be more than just the two I linked - and update them as well please?
There are some other log lines related to this issue:
e.g. these two, as
AddOrUpdateWorkload
callsAddOrUpdateWorkloadWithoutLock
Could you track those down - there may be more than just the two I linked - and update them as well please?
Yeah, I'll do that as well :)
Hey @mbobrovskyi and @gabesaba, The PR is still a work in progress, but I wanted to share what I've done so far and check if I'm on the right track. While working on it, I noticed a similar cache function here: workload_controller.go#L712. Should I update that as well? Also, for the test case, since I added a new parameter in the code, I think I'll need to update the test here: manager_test.go#L421. and I think I have to add a new parameter, am I right? Thanks!
Hey @mbobrovskyi and @gabesaba, The PR is still a work in progress, but I wanted to share what I've done so far and check if I'm on the right track. While working on it, I noticed a similar cache function here: workload_controller.go#L712. Should I update that as well? Also, for the test case, since I added a new parameter in the code, I think I'll need to update the test here: manager_test.go#L421. and I think I have to add a new parameter, am I right? Thanks!
Yeah, we need to update tests as well.
Hey @mbobrovskyi and @gabesaba, The PR is still a work in progress, but I wanted to share what I've done so far and check if I'm on the right track. While working on it, I noticed a similar cache function here: workload_controller.go#L712. Should I update that as well? Also, for the test case, since I added a new parameter in the code, I think I'll need to update the test here: manager_test.go#L421. and I think I have to add a new parameter, am I right? Thanks!
Yeah, we need to update tests as well.
I'll share it with you ASAP, Thanks! @mbobrovskyi
@7h3-3mp7y-m4n: The following test failed, say /retest
to rerun all failed tests or /retest-required
to rerun all mandatory failed tests:
Test name | Commit | Details | Required | Rerun command |
---|---|---|---|---|
pull-kueue-verify-main | 84d415a9f278ac3b992e00de3a849c413a901556 | link | true | /test pull-kueue-verify-main |
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
This PR added Log output for LocalQueue and ClusterQueue
Which issue(s) this PR fixes:
Fixes #3527
Special notes for your reviewer:
It added some log output for better debugging without breaking the function..
Does this PR introduce a user-facing change?
NONE