[CI Image] Update PyTorch to v1.10 in GPU image

[masahi]

• S0. The version on CI is 1.7, more than a year old

• S1. Tag of nightly build: TAG. Docker hub: https://hub.docker.com/layers/tlcpackstaging/ci_gpu/20220105-225914-79cfb797e

• S2. The nightly is built on TVM commit: 79cfb79

• S3. Testing the nightly image on ci-docker-staging: https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/ci-docker-staging/193/pipeline/

• S4. Retag TAG to VERSION:

docker pull tlcpackstaging/IMAGE_NAME:TAG
docker tag tlcpackstaging/IMAGE_NAME:TAG tlcpack/IMAGE_NAME:VERSION
docker push tlcpack/IMAGE_NAME:VERSION

• S5. Check if the new tag is really there: https://hub.docker.com/u/tlcpack

• S6. Submit a PR updating the IMAGE_NAME version on Jenkins [CI Image] Update PyTorch to v1.10 in GPU image  #9713

[manupak]

Hi @masahi ,

FYI, I'd be careful with S3.

I was trying to use the image from S2 in S3 as mentioned here : #9659
Unfortunately, it got a timeout and leaving the node with a image. It is only then I realize our jobs dont start with clean CI nodes in terms of images. Now the node does not have enough memory.

Now the ci_cpu upgrade is currently blocked on this and we dont have access to any of the nodes. cc : @leandron
#9705.

[masahi]

@manupa-arm Thanks, yes I'm aware of the recent CI outrage. Probably I'll work on this next week.

[leandron]

I can deal with this request in #9762.

[leandron]

#9762

[masahi]

@leandron This is for updating the GPU image, so I think it should be independent.

[masahi]

@manupa-arm @leandron @areusch I'm not familiar with the new CI image update protocol. How does one push an image to tlcpackstaging? I've tried

docker push tlcpackstaging/ci_gpu:20211219-100400-c0d326dbd

But got

denied: requested access to the resource is denied

Previously I would just create an image like ci_gpu:v0.76 and push it to tlcpack dockerhub org

[manupak]

@masahi you should not be needing to push images there. The ci-docker-build nighly job will automatically build images from a nightly checkout of main for all images, and push it there. The last number indicates the commit hash used when building the image

[masahi]

Interesting! I guess I don't even need to build a new image locally anymore... So should I just send a PR to update docker/install/ubuntu_install_onnx.sh to cause a new nightly image with the new PyTorch version to be built?

I have more CI questions I want to ask. Recently I've joined discord to learn about CI issues. Can we continue there?

[manupak]

Yes, that should do it.

S3 should capture any issues should the updated image breaks the current tests anyway.

As a next step, we want to explore the possibility to making every PR rebuild the images using tlcpackstaging images as a cache. i.e. we don't sacrifice correctness in the verification but the PRs that involves docker changes will be a bit slow due to the invalidation of the cache -- however, if we could push another tlcpackstaging image then it should be go back to normal behavior of using the cache. Something to discuss in the next meetup : @leandron @areusch

[masahi]

@jiangjiajun I'm testing a new image with PT 1.10 and getting an error from paddle: https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/ci-docker-staging/182/pipeline/

Any idea what's going on? I can run from_paddle.py locally without issues. free(): invalid pointer thing looks similar to a known issue with recent PT + LLVM discussed in #9362

[jiangjiajun]

It looks strange, I'll check this today