[x] Using the regular procedure I've been using to run the workflow (push a tag, manually run the build on that tag, move the tag when the build fails, etc.) I often observe the sccache plugin failing to find a usable cache when it's obviously there. Caches are branch-scoped, and GitHub doesn't exactly explain what happens when you build from a tag. I suspect it's important to do all our builds on a branch (usually main) and automatically create a tag/release when that workflow succeeds.
[ ] We might be able to get some cheap performance out of cacheing the llvm source checkout.
[ ] The build_tools job is ridiculously stable and delays observable feedback when working on the distribution job. We could probably find a way to cache the results of build_tools and skip most of the work.
In decreasing priority order:
main
) and automatically create a tag/release when that workflow succeeds.build_tools
job is ridiculously stable and delays observable feedback when working on thedistribution
job. We could probably find a way to cache the results ofbuild_tools
and skip most of the work.