Skip to content
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

Upgrade PyTorch version to v1.13.0 #2082

Merged
merged 2 commits into from
Jan 17, 2023

Conversation

tenzen-y
Copy link
Member

Signed-off-by: Yuki Iwai [email protected]

What this PR does / why we need it:
I upgraded PyTorch version to v1.13.0.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Checklist:

  • Docs included if any changes are user facing

@google-oss-prow
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tenzen-y

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

@tenzen-y
Copy link
Member Author

tenzen-y commented Jan 11, 2023

It seems that minikube image load is OOM killed..

@johnugeorge
Copy link
Member

@tenzen-y OOM Error is consistently happening

@tenzen-y
Copy link
Member Author

@tenzen-y OOM Error is consistently happening

Yes, that's right. I'm looking for a way to avoid OOM killed.

@tenzen-y
Copy link
Member Author

/hold


echo -e "\n\nLoading $CONTAINER_NAME image...\n\n"
minikube image load "$REGISTRY/$CONTAINER_NAME:$TAG"
DOCKER_BUILDKIT=1 minikube image build --build-opt platform=linux/amd64 --all -t "$REGISTRY/$CONTAINER_NAME:$TAG" -f "$DOCKERFILE" .
Copy link
Member Author

Choose a reason for hiding this comment

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

To avoid OOM errors in CI, we must build container images using minikube instead of docker.

Copy link
Member

Choose a reason for hiding this comment

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

What is the difference here?

Copy link
Member

Choose a reason for hiding this comment

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

The build succeeded but tests take longer time

Copy link
Member Author

Choose a reason for hiding this comment

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

@johnugeorge In minikube image build, we can build images using an actual container runtime on the minikube cluster. So we no longer load images to the minikube cluster.

Copy link
Member Author

@tenzen-y tenzen-y Jan 16, 2023

Choose a reason for hiding this comment

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

The build succeeded but tests take longer time

@johnugeorge As I can see, It seems to be faster.

2023-01-17 3 13 46

@johnugeorge
Copy link
Member

LGTM

/assign @andreyvelich

@tenzen-y
Copy link
Member Author

/hold cancel

@andreyvelich
Copy link
Member

Thank you for this improvement @tenzen-y !
/lgtm

@google-oss-prow google-oss-prow bot added the lgtm label Jan 17, 2023
@google-oss-prow google-oss-prow bot merged commit 0749265 into kubeflow:master Jan 17, 2023
@tenzen-y tenzen-y deleted the upgrade-python-version branch January 17, 2023 15:46
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.

3 participants