[CI] TVM cache is broken
See original GitHub issuehttps://github.com/microsoft/hummingbird/issues/586#issuecomment-1201529514_
Link to the CI result page: Add Python 3.10 · microsoft/hummingbird@3c52b20
TODO: investigate
ideas worth trying
- execute build even if TVM cache is hit
- try to create pip package and only cache it (do not cache the entire TVM directory)
- try ccache
- update
actions/cache@v1toactions/cache@v3
Issue Analytics
- State:
- Created a year ago
- Comments:6
Top Results From Across the Web
caching is broken in the pipeline · Issue #506 - GitHub
Unable to reserve cache with key Linux-1-tvm-0.7, another job may be creating this cache. which means our pipeline takes >40min each run. It ......
Read more >Tvm build issue in docker container - Questions
Their docker containers are broken. Workaround: inside a running container, follow steps to build from source documentation page. Once thats ...
Read more >[apache/incubator-tvm] Dev (#6775) - The Mail Archive
(#6381) * [DOCS] Fix the docker binary cache location (#6390) ... Fix Some Broken Web Links (#6475) * µTVM RPC server and Part...
Read more >Cisco Firepower Release Notes, Version 6.6 - Security
AppId looks up in dynamic cache even when it finds apps in a session ... while running SNMPWalk + S2S-IKEv2 and AnyConnect TVM...
Read more >Auto-tuning Matrix Multiplication and Convolution for Deep ...
loop split and fuse, loop unroll, loop reordering, vectorization, etc. ... For the cache complexity of CONV in TVM, we only need to...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Ah ok, nevermind. i see that on line 80 we always pip install Linux TVM now.
I was just trying to think back to a time when the cache worked more consistently and if something unexpected changed!
Apparently we can somehow clear it with the API