And the tests are just too long for the 50 minute limit. But if I can guarantee the single thread case then I can speed up the api annotations tests, by building a single exe to use for most of the tests.
On Mon, Jun 1, 2015 at 11:22 PM, Alan & Kim Zimmerman <[email protected]> wrote: > Looks like https://github.com/ghc/ghc/tree/wip/high_memory_usage has > passed. > > Interestingly it gathered all the tests marked that way for the end, and > ran them one at a time. > See https://api.travis-ci.org/jobs/64977719/log.txt?deansi=true > > On Mon, Jun 1, 2015 at 9:54 PM, Joachim Breitner <[email protected] > > wrote: > >> HI, >> >> Am Montag, den 01.06.2015, 14:42 -0500 schrieb Austin Seipp: >> > On Mon, Jun 1, 2015 at 2:34 PM, Joachim Breitner >> > > we are running validate with CPU=2, which I believe translates to >> > > THREADS=1. >> > >> > It's actually the opposite - if you check ./validate, CPU=2 translates >> > to THREAD=3! >> >> Eh, sorry, that’s what I meant. >> >> > Also, Thomas has alerted me that the testsuite actually has an option >> > called `high_memory_usage` which will serialize the tests and run them >> > one at a time. So actually, that can work as a solution too! >> >> Good idea. I just pushed a wip/ branch to test that. >> >> Greetings, >> Joachim >> >> >> -- >> Joachim “nomeata” Breitner >> [email protected] • http://www.joachim-breitner.de/ >> Jabber: [email protected] • GPG-Key: 0xF0FBF51F >> Debian Developer: [email protected] >> >> _______________________________________________ >> ghc-devs mailing list >> [email protected] >> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs >> >> >
_______________________________________________ ghc-devs mailing list [email protected] http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
