[CI Image] Update ci_cpu to v0.79

[Mousius]

• S0. Reason: Upcoming Conv2d support in CMSIS NN ([RFC][Tracking Issue] CMSIS-NN Integration #8646) and optimising the AOT tests ([AOT][Tests] Use pre-built libraries in Reference System tests #9271)

• S1. Tag of nightly build: 20211004-225913-779a50629. Docker hub: https://hub.docker.com/layers/tlcpackstaging/ci_cpu/20211004-225913-779a50629/images/sha256-aef4438e0a91d8b16a5da96f4c1885a1de8f386612077519dd491fce9b5b97d6?context=explore

• S2. The nightly is built on TVM commit: 95a20315d0d3403e5eea3bfe6ed5e942a51b169d. 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/77/pipeline

• S3. Testing the nightly image on ci-docker-staging

• S4. Retag 20211004-225913-779a50629 to v0.79:

docker pull tlcpackstaging/ci_cpu:20211004-225913-779a50629
docker tag tlcpackstaging/ci_cpu:20211004-225913-779a50629 tlcpack/ci-cpu:v0.79
docker push tlcpack/ci-cpu:v0.79

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

• S6. Submit a PR updating the ci-cpu version on Jenkins

[Mousius]

CC @ashutosh-arm @areusch

[areusch]

this tag isn't validated and it looks like we've been busted for a bit. investigating

[u99127]

S2 suggests only ci_gpu is busted as I pointed on discord - what am I missing @areusch ?

[leandron]

After some issues with other images such as ci_i386 and ci_gpu, I'm taking the task of running an ad hoc job to validate the latest ci_cpu (tlcpackstaging/ci_cpu:20211102-232503-054fff568) and tag it to be tlcpack/ci-cpu:v0.79 once it is validated.

Job: https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/ci-docker-staging/169/pipeline/

[leandron]

For record keeping, just to make it clear:

• tlcpackstaging/ci_cpu:20211102-232503-054fff568 became tlcpack/ci-cpu:v0.79

[manupak]

@areusch @tqchen @leandron, do we need to maintain v0.xx versioning ?

[areusch]

@manupa-arm it does seem like we could get rid of that. let's spin this into a discuss forum thread so that others can keep track. seems like we could do this but might want to add e.g. docker/publish.sh in case someone manually built images.