Skip to content

Conversation

@MaximilianAlgehed
Copy link
Collaborator

@MaximilianAlgehed MaximilianAlgehed commented Nov 13, 2025

This bring the mhs job down from a bit over 5 mins to a bit under 4, the majority of what's left is building mhs itself.

@MaximilianAlgehed
Copy link
Collaborator Author

@augustss Anything dangerous and/or stupid about what I'm doing here?

@MaximilianAlgehed
Copy link
Collaborator Author

Also, any chance of speeding up make minstall up by caching things?

@augustss
Copy link
Contributor

I'll take a look.

@sol
Copy link
Contributor

sol commented Dec 7, 2025

This bring the mhs job down from a bit over 5 mins to a bit under 4

Is it safe to share build products across mhs versions?

the majority of what's left is building mhs itself

#454 addresses this. (still pending upstream changes)

@MaximilianAlgehed
Copy link
Collaborator Author

Is it safe to share build products across mhs versions?

Good point - probably not in general.

#454 addresses this. (still pending upstream changes)

I'm glad your PR let's me elegantly get around the issue above! Thanks!

@sol
Copy link
Contributor

sol commented Dec 8, 2025

I think technically you could do nightly builds of mhs + all the libraries that are known to work and provide these via a GitHub action (Stackage-like).

This should make it as fast as it can get.

I'm gonna give this a try in a separate repository.

@sol
Copy link
Contributor

sol commented Dec 8, 2025

This brings the CI run down to 1m 26s.

@MaximilianAlgehed
Copy link
Collaborator Author

I expect this will make little to no difference after @sol's brilliant contribution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants