You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
CI: cache KGs/LPs/NCESData downloads with actions/cache #637
Suggested by @TheSheep-stack in #622: CI downloads KGs.zip, LPs.zip, NCESData.zip and CLIPData.zip from files.dice-research.org on every run (see .github/workflows/test.yml), and download speed is occasionally very slow.
Caching these with actions/cache (keyed on the archive URL/version) would cut CI time and remove the dependency on the file server being responsive for every run.
Not a bug and not blocking; split out of #622 once its root cause (DataLoader worker-pool deadlock, #614/#627/#628) was fixed.
1. Caching downloads (actions/cache): yes, let's do it. The gain is small (~2.5 min of a 35-45 min run), but the main benefit is that CI no longer depends on files.dice-research.org being fast on every run. I'd key the cache on a manual version string (e.g. ontolearn-data-v1) rather than the URL, since the archives change rarely and without notice.
2. 7-day eviction: acceptable. On a miss we just re-download. Note that caches are scoped per branch with fallback to the default branch, so develop needs to populate it for PRs to get hits (it does, since the workflow runs on every push).
3. Coverage only on PRs: I'd skip this. Coverage overhead is small compared to the learner tests, and the coverage report output isn't uploaded anywhere. The bigger free win is the trigger: on: [push, pull_request] runs the full suite twice for every PR branch push. Restricting push to develop/main and keeping pull_request should save more than anything else here.
4. Test parallelization: the only option that would materially cut the runtime, but also the riskiest:
tests/test_triplestore.py shares one Fuseki dataset, so those tests would need to stay in a single worker (--dist loadgroup + xdist_group).
Some tests write to shared paths (Predictions_*.owl, weights, Experiments/), which could collide across workers.
Standard runners have only 4 vCPUs and torch already uses multiple threads, so the speedup may be well under 4x.
A safer alternative is splitting test files across matrix jobs (learners / neural / triplestore). That needs no test changes, but each job restores the data cache, which is another reason to do (1) first.
Proposed order: (1) add the cache step, closing this issue; (2) fix the duplicate push/PR triggers; (3) open a separate issue for parallelization, trying the matrix split before xdist.
Activity
TheSheep-stack commentedon Oct 16, 2026
What do you think @Demirrr
Demirrr commentedon Oct 16, 2026
Thanks @TheSheep-stack, my thoughts on your points:
1. Caching downloads (
actions/cache): yes, let's do it. The gain is small (~2.5 min of a 35-45 min run), but the main benefit is that CI no longer depends onfiles.dice-research.orgbeing fast on every run. I'd key the cache on a manual version string (e.g.ontolearn-data-v1) rather than the URL, since the archives change rarely and without notice.2. 7-day eviction: acceptable. On a miss we just re-download. Note that caches are scoped per branch with fallback to the default branch, so
developneeds to populate it for PRs to get hits (it does, since the workflow runs on every push).3. Coverage only on PRs: I'd skip this. Coverage overhead is small compared to the learner tests, and the
coverage reportoutput isn't uploaded anywhere. The bigger free win is the trigger:on: [push, pull_request]runs the full suite twice for every PR branch push. Restrictingpushtodevelop/mainand keepingpull_requestshould save more than anything else here.4. Test parallelization: the only option that would materially cut the runtime, but also the riskiest:
tests/test_triplestore.pyshares one Fuseki dataset, so those tests would need to stay in a single worker (--dist loadgroup+xdist_group).Predictions_*.owl, weights,Experiments/), which could collide across workers.A safer alternative is splitting test files across matrix jobs (learners / neural / triplestore). That needs no test changes, but each job restores the data cache, which is another reason to do (1) first.
Proposed order: (1) add the cache step, closing this issue; (2) fix the duplicate push/PR triggers; (3) open a separate issue for parallelization, trying the matrix split before
xdist.