Building haddocks causes GitHub actions to go out of memory?

Has anyone noticed that building haddocks on GitHub Actions causes an out of memory condition? It specifically seems to occur on 9.0-9.6 but not 8.8 and 8.10. Here are a couple of runs showing the behavior:

The error message is “Error: Process completed with exit code 143.” 143 is SIGTERM, which I expect was sent by some supervisor process on an out of memory condition.

And here’s a run where I disabled building haddocks. Everything builds fine[1]:

The specific Haddock command that I’m running is cabal v2-haddock --haddock-hoogle. I don’t expect this has anything to do with GitHub Actions specifically, it’s just that that is a low-memory environment so it will trigger an out of memory condition much more easily.

[1] But interestingly 9.0-9.6 take 7-10 minutes to build and test, whereas 8.8 and 8.10 take 2-3 minutes.

2 Likes

perhaps relevant issues?

3 Likes

Very helpful, thanks! I haven’t had the time to chase this up yet, but I will look in more detail when I next try to get these Haddocks building.