Re: On CI

2021-02-22 Thread John Ericson
I agree one should be able to get most of the testing value from stage1. And the tooling team at IOHK has done some work in https://gitlab.haskell.org/ghc/ghc/-/merge_requests/3652 to allow a stage 1 compiler to be tested. That's a very important first step! But TH and GHCi require either

Re: Changes to performance testing?

2021-02-22 Thread Andreas Klebinger
This seems quite reasonable to me. Not sure about the cost of implementing it (and the feasability of it if/when merge-trains arrive). Andreas Am 21/02/2021 um 21:31 schrieb Richard Eisenberg: On Feb 21, 2021, at 11:24 AM, Ben Gamari mailto:b...@well-typed.com>> wrote: To mitigate this I

Re: On CI

2021-02-22 Thread Spiwack, Arnaud
Let me know if I'm talking nonsense, but I believe that we are building both stages for each architecture and flavour. Do we need to build two stages everywhere? What stops us from building a single stage? And if anything, what can we change to get into a situation where we can? Quite better than

RE: On CI

2021-02-22 Thread Simon Peyton Jones via ghc-devs
Incremental CI can cut multiple hours to < mere minutes, especially with the test suite being embarrassingly parallel. There simply no way optimizations to the compiler independent from sharing a cache between CI runs can get anywhere close to that return on investment. I rather agree with