Richard Eisenberg <[email protected]> writes: > Hi devs, > > Is Harbormaster acting up? I saw today two out-of-memory failures, > including this one > (https://phabricator.haskell.org/harbormaster/build/9150/), which > happens when building the stage-1 compiler. That means that an > off-the-shelf GHC is the one that's running out of memory. > > Separately, a comments-only patch didn't validate > (https://phabricator.haskell.org/harbormaster/build/9148/). > Yes, Harbormaster has been stuggling a great deal recently due to the high volume of commits and differentials that we have been experiencing leading up to the feature freeze.
Of course, in principle this shouldn't result in validations failing. Sadly, Harbormaster leaves a great deal to be desired when it comes to resource management as there is no way to limit the number of concurrent builds which which it launches. Consequently even our quite substantial build machine eventually starts thrashing under high patch volume. I have some ideas on how to rework our build process to work around this insanity but I'm very much out of bandwidth at the moment. It certainly won't happen before next week. Cheers, - Ben
signature.asc
Description: PGP signature
_______________________________________________ ghc-devs mailing list [email protected] http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
