Re: Scaling back CI (for now)?

That aside, the CIs don't seem stable at all. Frequent timeouts even before they start. I have been trying to merge 3 changes for a while now and everytime one of them times out and I have to restart the timed out ones. Then there are merge conflicts and I have to start over. This is "bot wackamole" :) On Sun, Feb 3, 2019, 13:56 Matthew Pickering wrote:

It has been established today that Marge is failing to run in batch mode for some reason which means it takes at least as long as CI takes to complete for each commit to be merged. The rate is about 4 commits/day with the current configuration.

On Sat, Feb 2, 2019 at 7:57 PM Sebastian Graf wrote:

...

Hi,

Am Sa., 2. Feb. 2019 um 16:09 Uhr schrieb Matthew Pickering <

matthewtpickering@gmail.com>:

...

...

All the other flavours should be run once the commit reaches master.

Thoughts?

That's even better than my idea of only running them as nightlies. In favor!

...

Cheers,

Matt _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

---

ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs