Skip to content

[Codeflare Action] Update notebook's pipfile to sync with Codeflare-SDK release 0.21.1 #719

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

Conversation

codeflare-machine-account
Copy link
Contributor

🚀 This is an automated Pull Request.

This PR updates the Pipfile to sync with latest Codeflare-SDK release.

Copy link
Member

@harshad16 harshad16 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve
👍

Copy link
Contributor

openshift-ci bot commented Sep 27, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: harshad16

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Copy link
Contributor

openshift-ci bot commented Sep 27, 2024

@codeflare-machine-account: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/runtime-rocm-pytorch-ubi9-python-3-11-pr-image-mirror 736adf6 link true /test runtime-rocm-pytorch-ubi9-python-3-11-pr-image-mirror
ci/prow/notebook-cuda-jupyter-ds-ubi9-python-3-11-pr-image-mirror 736adf6 link true /test notebook-cuda-jupyter-ds-ubi9-python-3-11-pr-image-mirror
ci/prow/runtimes-ubi9-e2e-tests 736adf6 link true /test runtimes-ubi9-e2e-tests
ci/prow/rocm-runtimes-ubi9-e2e-tests 736adf6 link true /test rocm-runtimes-ubi9-e2e-tests
ci/prow/rocm-notebooks-e2e-tests 736adf6 link true /test rocm-notebooks-e2e-tests
ci/prow/notebooks-ubi9-e2e-tests 736adf6 link true /test notebooks-ubi9-e2e-tests
ci/prow/notebook-rocm-jupyter-pyt-ubi9-python-3-11-pr-image-mirror 736adf6 link true /test notebook-rocm-jupyter-pyt-ubi9-python-3-11-pr-image-mirror
ci/prow/images 736adf6 link true /test images

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Copy link
Member

@jstourac jstourac left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn't update the python 3.9 images, which, I presume, is expected on this branch.

But one question - I can see that intel/runtimes/ml/... is updated but the rest of the Intel images are not:

$ grep -r "codeflare-sdk = " | grep -v "0.21.1" | grep -v "\-3.9"
jupyter/intel/pytorch/ubi9-python-3.11/Pipfile.cpu:codeflare-sdk = "~=0.13.0"
jupyter/intel/pytorch/ubi9-python-3.11/Pipfile.gpu:codeflare-sdk = "~=0.13.0"
jupyter/intel/tensorflow/ubi9-python-3.11/Pipfile.cpu:codeflare-sdk = "~=0.13.0"
jupyter/intel/tensorflow/ubi9-python-3.11/Pipfile.gpu:codeflare-sdk = "~=0.13.0"
intel/runtimes/pytorch/ubi9-python-3.11/Pipfile.cpu:codeflare-sdk = "~=0.13.0"
intel/runtimes/pytorch/ubi9-python-3.11/Pipfile.gpu:codeflare-sdk = "~=0.13.0"
intel/runtimes/tensorflow/ubi9-python-3.11/Pipfile.cpu:codeflare-sdk = "~=0.13.0"
intel/runtimes/tensorflow/ubi9-python-3.11/Pipfile.gpu:codeflare-sdk = "~=0.13.0"

First I thought, that we don't intend to touch the images from Intel as we don't maintain them. But since we touch at least one of them, we should update all, no?

I presume that the reason the others aren't updated is because the Pipfile is actually named as Pipfile.cpu or Pipfile.gpu which was discussed some time ago and the fix was supposed to be in place for this already, see project-codeflare/codeflare-sdk#645.

Looks like there was some refactor 2 weeks ago project-codeflare/codeflare-sdk#655 which broke that, see lines 61 and 79. This can be seen in the execution also, see multiple errors here:

line 5: 2: command not found

Update: I raised this one project-codeflare/codeflare-sdk#691 to fix it. I didn't try it, but I suspect that after that fix, also 3.9 images will get updated with the next round.

@@ -4,13 +4,11 @@ verify_ssl = true
name = "pypi"

[packages]
# Classical-ML
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@harshad16 are we okay we're loosing these comment lines? 🤔

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've added a fix for that here

@openshift-merge-robot
Copy link
Contributor

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@jstourac
Copy link
Member

jstourac commented Oct 2, 2024

@KPostOffice do you think it would be possible to close this PR and raise a new one with the latest changes applied to the relevant GHA? 🤔

@harshad16
Copy link
Member

As the codeflare-sdk github action failed: https://github.com/project-codeflare/codeflare-sdk/actions/runs/11134262380
created a separate PR for now: #725

@jstourac
Copy link
Member

jstourac commented Oct 3, 2024

As the codeflare-sdk github action failed: https://github.com/project-codeflare/codeflare-sdk/actions/runs/11134262380 created a separate PR for now: #725

@harshad16 The GHA failed during upgrade of this directory:

--Processing directory 20 'notebooks/jupyter/rocm/tensorflow/ubi9-python-3.9' of total 34

I wonder - do we want to update these 3.9 python based images or can we remove that python version from the GHA and update only 3.11 based images from now on?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants