-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[CI Image] Update ONNX #9511
Comments
Hi @AndrewZhaoLuo, Do you know which images we need to be updated here? I think it's |
Yup I think thats correct |
cc @areusch do I need to do anything else? I can't push the new versions to tlcpack (I get error denied) |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Our current ONNX version is 1.8.1. The latest version is 1.10.2. Most notably, opsets 14-16 have been added to the spec. We should support some of these operators since they include some common activation like HardSwish
S0.
S1. Tag of nightly build. Docker hub: https://hub.docker.com/layers/tlcpackstaging/ci_cpu/...
ci_gpu
: https://hub.docker.com/layers/tlcpackstaging/ci_gpu/20211120-225913-0cb633777/images/sha256-8d1318e2b65fbf89a997fd6a3435532ef89408bc0d3ad2e0660358cacaba1580?context=exploreci_qemu
: https://hub.docker.com/layers/tlcpackstaging/ci_qemu/20211128-225913-18c88789a/images/sha256-84280804918b9db81c91ae777963f169562e3dd4bceae99e5f6d371d55e7fd72?context=exploreS2. The nightly is built on TVM commit: TVM_COMMIT. Detailed info can be found here: https://ci.tlcpack.ai/blue/organizations/jenkins/docker-images-ci%2Fdaily-docker-image-rebuild/detail/daily-docker-image-rebuild/130/pipeline
18c88789a70489d6615234f25bcc4f29e9dd83dc
which is far after the indicated commitS3. Testing the nightly image on ci-docker-staging: https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/ci-docker-staging/...
S4. Retag TAG to 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
The text was updated successfully, but these errors were encountered: