too long setup phase & caching
See original GitHub issueQuite frequently we have failing test just after init of Conda environment. From the log, it seems to be cancelled but there is no obvious reason why it happened and I do not think that anyone did it manually… This is a link to one of this pseudo cancelled jobs https://github.com/PyTorchLightning/pytorch-lightning/pull/2486/checks?check_run_id=847392959 and this is the cut log
2020-07-07T21:19:14.8870348Z ##[group]Run goanpeca/setup-miniconda@v1.6.0
2020-07-07T21:19:14.8870519Z with:
2020-07-07T21:19:14.8870641Z auto-activate-base: false
2020-07-07T21:19:14.8870762Z miniconda-version: 4.7.12
2020-07-07T21:19:14.8870877Z python-version: 3.7
2020-07-07T21:19:14.8870975Z environment-file: environment.yml
2020-07-07T21:19:14.8871096Z activate-environment: pl-env
2020-07-07T21:19:14.8871213Z use-only-tar-bz2: true
2020-07-07T21:19:14.8871332Z auto-update-conda: false
2020-07-07T21:19:14.8871449Z remove-profiles: true
2020-07-07T21:19:14.8871561Z ##[endgroup]
2020-07-07T21:19:14.9800149Z
2020-07-07T21:19:14.9800380Z #
2020-07-07T21:19:14.9800612Z # Downloading Miniconda...
2020-07-07T21:19:14.9800680Z
2020-07-07T21:19:14.9805777Z ##############################
2020-07-07T21:19:14.9805898Z
2020-07-07T21:19:14.9809615Z Miniconda3-4.7.12-Linux-x86_64.sh
2020-07-07T21:19:15.9515494Z Saving cache...
2020-07-07T21:19:16.6935049Z
2020-07-07T21:19:16.6935850Z # Installing Miniconda...
2020-07-07T21:19:16.6936568Z #########################
2020-07-07T21:19:16.6937014Z
2020-07-07T21:19:16.6999519Z [command]/usr/bin/bash /home/runner/work/_temp/64e1902d-ffc0-4207-b662-496b67f44c2e.sh -b -p /usr/share/miniconda3
2020-07-07T21:19:17.3422900Z PREFIX=/usr/share/miniconda3
2020-07-07T21:19:18.1341837Z Unpacking payload ...
2020-07-07T21:19:19.3115710Z
2020-07-07T21:38:25.4494202Z 0%| | 0/35 [00:00<?, ?it/s]
2020-07-07T21:38:25.4781118Z ##[error]The operation was canceled.
Any idea what could be happening there?
Issue Analytics
- State:
- Created 3 years ago
- Comments:24 (12 by maintainers)
Top Results From Across the Web
GitLab CI: Cache and Artifacts explained by example
Nobody wants to wait for the CI completion too much, it's better to set up all the tweaks to avoid long waiting between...
Read more >Caching general build artifacts between stages - GitLab.org
Caching is to speed-up the setup of build dependencies. There is no guarantee that the cache will be there. You're looking for artifact...
Read more >Caching dependencies to speed up workflows - GitHub Docs
Use caching when you want to reuse files that don't change often between jobs or workflow runs, such as build dependencies from a...
Read more >Best practices for writing Dockerfiles - Docker Documentation
Because an image is built during the final stage of the build process, you can minimize image layers by leveraging build cache. For...
Read more >Mirrors and Binary Caches Tutorial
This could happen for a variety of reasons. Maybe you're building on a compute node that isn't connected to the greater internet, or...
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 FreeTop 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
Top GitHub Comments
Ok, I was checking some other log from the master which took 9min but could be because of an invalid cache… I m no testing the
use-mamba: true
🐰Hm, wait, the last logs do show how
mamba
is hitting the cache: https://github.com/PyTorchLightning/metrics/runs/3348696215?check_suite_focus=true#step:7:462