-
Notifications
You must be signed in to change notification settings - Fork 701
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Re-enable Windows CI #10282
Re-enable Windows CI #10282
Conversation
38d80da
to
d7d1548
Compare
0e1a187
to
dee8a63
Compare
dee8a63
to
6eb259b
Compare
I looked there but couldn't connect your last comment there and this PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see now that you made a great summary on Matrix:
I have a proposal for the CI Windows issues. It turns out that enabling io-manager=native for Windows makes all tests pass for all exercised GHCs except 9.0.2 which crashes with an access violation.
However not enabling the io-manager results in random GHCs failing with
fd: hGetLine: end of input
exceptions.My proposal is to disable the 9.0.2 validate job for Windows and enable io-manager=native for all other GHCs. We are already disabling 8.10.7 and 8.8.4 on Windows.
That works, I guess. Although this practically means that we aren't really delivering on that 5-year support window...
6eb259b
to
7f0ce61
Compare
Cherry-picked from #10282 so CI will pass.
Cherry-picked from #10282 so CI will pass.
Can we do something stupid like wrapping ghci with something that always exits successfully? |
9c2d14d
to
4aade2d
Compare
@mergify backport 3.12 |
✅ Backports have been created
|
This PR disables the 9.0.2 validate job for Windows and provides
--io-manager=native
for every other GHC. See #9571 for the reasons.