Closed mcbarton closed 2 months ago
Why are we still building a cache for clang-18? Should we not get it via the package manager?
Why are we still building a cache for clang-18? Should we not get it via the package manager?
We can get rid of it via a package manager, but not for all systems yet (osx Homebrew doesn't currently have llvm 18, but its in progress). Its also not available through Emscripten forge yet for the web assembley. I think we'll be able to remove the llvm 18 cache, but not for a few weeks. This PR should significantly reduce the size of the cache if it works. The cache will also be reduce even more when I put in my PR which removes the osx x86 jobs.
@vgvassilev I won't be able to be certain this PR works until the cache is cleared and the workflow is run manually.
Yes, just waiting for a job to finish and I will merge it.
Yes, just waiting for a job to finish and I will merge it.
I wouldn't merge this one yet until its been able to be tested. I'm not 100 % sure this PR works.
Yes, just waiting for a job to finish and I will merge it.
I wouldn't merge this one yet until its been able to be tested. I'm not 100 % sure this PR works.
I reran with the cache cleared and indeed you are right we might need to improve this PR.
@vgvassilev can you clear the cache and rerun this PR?
Done.
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 79.25%. Comparing base (
e639070
) to head (b598dbb
). Report is 7 commits behind head on main.
@vgvassilev This PR is ready for merging. I recommend clearing the cache before merging.
@vgvassilev can you clear the cache, and then manually rerun the workflow of this PR? It should pass, while having a reduced llvm cache, based on the workflow in xeus-clang-repl.