-
Notifications
You must be signed in to change notification settings - Fork 41
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
Defer retrieving GetRayJobId in test #89
Conversation
/lgtm |
That makes me think whether we should update the Ray API helper function signatures to take the Job namespace and name, instead of the Job id, and do the retrieval from within the helper function. |
/approve |
@astefanutti The problem is that there are two options of submitting the job - CR or REST API. In case of REST API there is no CR created, so helper wouldn't be able to obtain job id in that case from namespace and name. |
Ah right. So we could (re-)add the |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: astefanutti, winklerm 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 |
GetRayJobId call needs to be deferred to make sure that job id is stored by KubeRay cluster.
Description
TestRayCluster test was failing on log storage line. Log storage function was deferred, however its arguments are resolved in realtime, causing GetRayJobId to be resolved before KubeRay operator had a chance to store job id in RayJob CR.
Moving the whole log storage line into separate function makes sure that RayJob CR is fully initialized.
How Has This Been Tested?
Manually.
Merge criteria: