
Both Tamar and Omer are right.
* Not doing CI on Windows is bad. It means that bugs get introduced, and not discovered until later. This is Tamer’s point, and it is valid.
* Holding up MRs because a failures in Windows CI that is unrelated to the MR is also bad. It a frustrating waste of time, and discourages all authors. (In contrast, holding up an MR because it introduces a bug on Windows is fine, indeed desirable.) This is Omer’s point, and it is valid.
The obvious solution is: let’s fix Windows CI, so that it doesn’t fail except when the MR genuinely introduces a bug.
How hard would it be to do that? Do we even know what the problem is?
Simon
From: ghc-devs
Sure because only testing once every 6 months is a very very good idea...
Sent from my Mobile
On Fri, Jan 17, 2020, 06:03 Ömer Sinan Ağacan
mailto:omeragacan@gmail.com> wrote: Hi Ben,
Can we please disable Windows CI? I've spent more time fighting the CI than doing useful work this week, it's really frustrating.
Since we have no idea how to fix it maybe we should test Windows only before a release, manually (and use bisect in case of regressions).
Ömer
Ben Gamari
mailto:ben@smart-cactus.org>, 14 Oca 2020 Sal, 14:30 tarihinde şunu yazdı: Hi all,
Currently Windows CI is a bit flaky due to some unfortunately rather elusive testsuite driver bugs. Progress in resolving this has been a bit slow due to travel over the last week but I will be back home tomorrow and should be able to resolve the issue soon thereafter.
Cheers,
- Ben _______________________________________________ ghc-devs mailing list ghc-devs@haskell.orgmailto:ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devshttps://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmail.haskell.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc-devs&data=02%7C01%7Csimonpj%40microsoft.com%7C20b2daaf0e674142e41508d79b1968ad%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637148405761605935&sdata=VmLpBxMbcYWYHaa34KpF1ju2SURx%2BOb5C5g5Gi7YoGE%3D&reserved=0
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.orgmailto:ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devshttps://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmail.haskell.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc-devs&data=02%7C01%7Csimonpj%40microsoft.com%7C20b2daaf0e674142e41508d79b1968ad%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637148405761610933&sdata=z28IhdWnHfBKvYTakK6lh8qhr4VPMUBzl71RXBrYkqA%3D&reserved=0