-
Notifications
You must be signed in to change notification settings - Fork 77
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
Remove requirments-elyra.txt from the code base #761
Remove requirments-elyra.txt from the code base #761
Conversation
33dc7a7
to
ff9bdeb
Compare
ff9bdeb
to
906368e
Compare
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.
I thought we decided to keep these files present, just delete the content. Has anything changed?
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.
Empty out "*/utils/requirements-elyra.txt", with comments to keep it for sanity
remove all "/kustomize/base/requirements-elyra.txt"
hmm
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.
Ahhh I see will revert it back! Sorry about that
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.
Empty out "*/utils/requirements-elyra.txt", with comments to keep it for sanity
remove all "/kustomize/base/requirements-elyra.txt"
This is old summary. Last time we discussed on the scrum to keep the /utils/requirements-elyra.txt
and put its content in comments, because otherwise the bootstraper.py
will fail.
8584bc1
to
6f26350
Compare
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.
Great initiative, shared some comments
Makefile
Outdated
$(KUBECTL_BIN) exec runtime-pod -- /bin/sh -c "python3 -m pip install -r /opt/app-root/elyra/requirements-elyra.txt && \ | ||
curl https://raw.githubusercontent.com/nteract/papermill/main/papermill/tests/notebooks/simple_execute.ipynb --output simple_execute.ipynb && \ | ||
python3 -m papermill simple_execute.ipynb output.ipynb > /dev/null" ; \ | ||
$(KUBECTL_BIN) exec runtime-pod -- /bin/sh -c "python3 -m pip install pipenv --three sync && \ |
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.
$(KUBECTL_BIN) exec runtime-pod -- /bin/sh -c "curl https://raw.githubusercontent.com/opendatahub-io/elyra/refs/heads/main/etc/generic/requirements-elyra.txt --output req.txt && \ python3 -m pip install -r req.txt && \
curl https://raw.githubusercontent.com/nteract/papermill/main/papermill/tests/notebooks/simple_execute.ipynb --output simple_execute.ipynb && \
python3 -m papermill simple_execute.ipynb output.ipynb > /dev/null" ; \
Try this.
As, the reason for using the requirements.txt is so that , we can make sure that packages are installable ,
perhaps, we can extend this in further tasks, to do some extra checks.
runtimes/datascience/ubi9-python-3.11/utils/requirements-elyra.txt
Outdated
Show resolved
Hide resolved
5382208
to
e8d535f
Compare
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.
@dibryant , can you please add fail=0 ; \
below line number 522
as i believe we missed it and line 546 complain 😅
7e917dd
to
2144737
Compare
runtimes/minimal/ubi9-python-3.11/kustomize/base/requirements-elyra.txt
Outdated
Show resolved
Hide resolved
89fda11
to
b69c78a
Compare
7f531fa
to
8a39449
Compare
./runtimes/rocm-tensorflow/ubi9-python-3.11/kustomize/base/kustomization.yaml Error: 11:1 [empty-lines] too many blank lines (1 > 0) ./runtimes/tensorflow/ubi9-python-3.11/kustomize/base/kustomization.yaml Error: 11:1 [empty-lines] too many blank lines (1 > 0) and wrongly intended line in Makefile, that's not linted automatically
8a39449
to
b8a628f
Compare
without it, pip would error out on this invalid requirements file
bf3931e
to
844aaa6
Compare
Checked this with github actions in https://github.com/jiridanek/notebooks/actions/runs/12045657286/job/33585360434, the results look good, only failures there are known issues in cuda/rocm images. This PR is not removing elyra-requirements.txt from python3.9 images and from the intel runtimes, but that's ok. We want to delete the python3.9 images from main anyways, and we don't touch intel because it's broken (https://issues.redhat.com/browse/RHOAIENG-8388) /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jiridanek 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 |
/label tide/merge-method-squash to squash all commits on the PR together |
/override "build (rocm-jupyter-pytorch-ubi9-python-3.11) / build" This is due to known issue |
@jiridanek: Overrode contexts on behalf of jiridanek: build (rocm-jupyter-pytorch-ubi9-python-3.11) / build, build (rocm-jupyter-pytorch-ubi9-python-3.9) / build In response to this:
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. |
ROCm images are failing to build on ephemeral-storage issues, e.g.
/override ci/prow/rocm-runtimes-ubi9-e2e-tests |
@jiridanek: Overrode contexts on behalf of jiridanek: ci/prow/rocm-runtimes-ubi9-e2e-tests, ci/prow/runtimes-ubi9-e2e-tests In response to this:
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. |
/retest |
eff0195
into
opendatahub-io:main
/test ci/prow/runtimes-ubi9-e2e-tests |
…761 (comment) when merging the work
…ebooks Github Actions (#775) * RHOAIENG-16076: tests(gha): run Makefile tests in GitHub Actions * fixup, looks like I lost the second changed line from #761 (comment) when merging the work * fixup, linter wants space in the comments; IntelliJ is ok with it, so let's do that * fixup, add reference to OpenShift CI for the source of the make invocations * fixup, the ifNotPresent pull policy (for PR checks without image registry) and the symbolic links apparently needed to deploy rocm stuff
Good idea, I've been putting in the required libraries from requirements-elyra.txt upstream into the main requirements file / Pipfile when building Jupyterlab images and runtime images for a long time now. With that and the commented-out install at runtime in bootstrapper.py upstream notice, the issue is fixed and Elyra has all it needs even at runtime in Airflow and KFP. I also introduced a new env var that makes output of file run logs optional to S3. |
…ebooks Github Actions (opendatahub-io#775) * RHOAIENG-16076: tests(gha): run Makefile tests in GitHub Actions * fixup, looks like I lost the second changed line from opendatahub-io#761 (comment) when merging the work * fixup, linter wants space in the comments; IntelliJ is ok with it, so let's do that * fixup, add reference to OpenShift CI for the source of the make invocations * fixup, the ifNotPresent pull policy (for PR checks without image registry) and the symbolic links apparently needed to deploy rocm stuff (cherry picked from commit b3d8af0)
…books Github Actions (opendatahub-io#775) * RHOAIENG-16076: tests(gha): run Makefile tests in GitHub Actions * fixup, looks like I lost the second changed line from opendatahub-io#761 (comment) when merging the work * fixup, linter wants space in the comments; IntelliJ is ok with it, so let's do that * fixup, add reference to OpenShift CI for the source of the make invocations * fixup, the ifNotPresent pull policy (for PR checks without image registry) and the symbolic links apparently needed to deploy rocm stuff (cherry picked from commit b3d8af0)
…ebooks Github Actions (opendatahub-io#775) * RHOAIENG-16076: tests(gha): run Makefile tests in GitHub Actions * fixup, looks like I lost the second changed line from opendatahub-io#761 (comment) when merging the work * fixup, linter wants space in the comments; IntelliJ is ok with it, so let's do that * fixup, add reference to OpenShift CI for the source of the make invocations * fixup, the ifNotPresent pull policy (for PR checks without image registry) and the symbolic links apparently needed to deploy rocm stuff
Fixes for https://issues.redhat.com/browse/RHOAIENG-11068
Description
Remove requirments-elyra.txt from the code base
How Has This Been Tested?
@jiridanek:
make
tests for imagesMerge criteria: