CI: Updated cached paths for cabal
and update Haskell config action dep
#399
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Contributes to #375
cabal
cache. It looks like @JasonGross had the right idea.I don't think this PR closes #375 because it doesn't have an Agda build cache, so building
agda-categories
is still completely fresh for each CI run, so we can have a look at that too.To audit this solution, please have a look at my fork's CI runs, specifically the earliest 2's build times and logs. The first one is a completely fresh run without a cache, and the second one has a cache. There's a ~20min time cut with the cache hit, but I would hope that it can be brought down further by adding the Agda build cache to the CI cache too.