-
Notifications
You must be signed in to change notification settings - Fork 176
Fixing test flake #1534
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
Fixing test flake #1534
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kfswain 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 |
✅ Deploy Preview for gateway-api-inference-extension ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
p.wg.Add(1) | ||
go func() { | ||
p.indexer.Add(state.PrefixHashes, ServerID(targetPod.NamespacedName)) | ||
p.wg.Done() |
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.
mmmmmm.
this fix introduces a wg only for test purpose. the thing is we don't have access to this wg outside of prefix plugin package, so llm-d tests will fail (we test PD, where prefix is used and profile handler uses it, reads state from CycleState, but with this go routine the update is not ready on time.
it solves the issue only in prefix unit tests
as temp fix to unblock flaky tests this is good enough as we don't want to fail incoming PRs. /lgtm |
/hold @kfswain you know what - maybe we can make the WG public? as long as we have this solution in place, I'll need to add wg.wait also in llm-d unit tests |
discussed with kellen, this will be handled in a follow up. /unhold |
Fixes: #1529
Adding a waitGroup should not impact prod code as we do not wait on this WG anywhere in the system, just allows unit tests to be synchronous