hashar created this task. hashar added projects: Continuous-Integration-Infrastructure, Castor, Pywikibot. Restricted Application added subscribers: pywikibot-bugs-list, Aklapper.
TASK DESCRIPTION I have noticed a build of the Jenkins job pywikibot-core-tox <https://integration.wikimedia.org/ci/job/pywikibot-core-tox/> that spent a lot of time syncing the cache. The namespace is `CASTOR_NAMESPACE="pywikibot-core/master/pywikibot-core-tox"`, looking at the #castor <https://phabricator.wikimedia.org/tag/castor/> instance: ssh integration-castor05.integration.eqiad1.wikimedia.cloud sudo du -m -d1 /srv/castor/pywikibot-core/master/pywikibot-core-tox 1182 /srv/castor/pywikibot-core/master/pywikibot-core-tox/pip 60 /srv/castor/pywikibot-core/master/pywikibot-core-tox/virtualenv 11446 /srv/castor/pywikibot-core/master/pywikibot-core-tox/pre-commit 12688 /srv/castor/pywikibot-core/master/pywikibot-core-tox pre-commit stores caches there that keeps accumulating. Some of the cache directories take 189MB, they a couple pyenv: 94 ./py_env-python3.10 95 ./py_env-python3.13 I don't think we should store them, or at least they should not be accumulating them? For the tox/pip part, we only save and restore the pip cache, the venv are reinstalled from scratch on each build. TASK DETAIL https://phabricator.wikimedia.org/T422242 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/
_______________________________________________ pywikibot-bugs mailing list -- [email protected] To unsubscribe send an email to [email protected]
