Build time over travis time limit again

Hi, in case you are getting failed build reports from Travis and are wondering what’s wrong: Since a few commits our gradually increasing build time seems to have hit the next Travis build time limit (which was already raised to 70 minutes for us). I tried a few obvious knobs, but none of them would help. I will ask for more time from them. But if you know a way to keep build times down, that’d be great. Does Hadrian speed up a build from scratch? Greetings, Joachim -- Joachim “nomeata” Breitner mail@joachim-breitner.de • https://www.joachim-breitner.de/ XMPP: nomeata@joachim-breitner.de • OpenPGP-Key: 0xF0FBF51F Debian Developer: nomeata@debian.org

Hi, Am Dienstag, den 07.02.2017, 18:09 -0500 schrieb Joachim Breitner:
I will ask for more time from them. But if you know a way to keep build times down, that’d be great.
we got 90 minutes now…
Due to the broken window effect, we now have two failures:
TH_addCStub1(normal) 4122 of 5714 [0, 0, 0]--- /tmp/ghctest-u7xmp5/test spaces/./th/TH_addCStub2.run/TH_addCStub2.stderr.normalised 2017-02-09 17:41:03.087318367 +0000
+++ /tmp/ghctest-u7xmp5/test spaces/./th/TH_addCStub2.run/TH_addCStub2.comp.stderr.normalised 2017-02-09 17:41:03.087318367 +0000
@@ -1,6 +1,4 @@
TH_addCStub2.hs:13:13:
expected ‘;’, ‘,’ or ‘)’ before ‘{’ token
- [ "#include
participants (1)
-
Joachim Breitner