driazati commented on issue #11785:
URL: https://github.com/apache/tvm/issues/11785#issuecomment-1162220529

   > If not we can just wait until #11768 that removes this two PR based flow 
of updating docker.
   
   just fyi #11768 doesn't actually do this, it just automates some of the pain 
away (image bumps are still manual but a bot will file the PR instead of a 
person, CI will update/tag images in Docker Hub as they come along) and should 
hopefully catch issues like this by running CI with the new images on PRs where 
`docker/*` files are changed. We decided against using newly built images every 
time in as in #11673 since external dependencies could then break CI at any 
time rather than be gated behind an update


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to