-
Notifications
You must be signed in to change notification settings - Fork 697
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
Use --io-manager=native
in lib-suite
on Windows
#10114
Use --io-manager=native
in lib-suite
on Windows
#10114
Conversation
d799936
to
416255f
Compare
416255f
to
ed0cac8
Compare
6f71d6e
to
ae5c57e
Compare
This PR fails consistently in CI for GHC 9.0.2 with a Mingw error.
However I cannot reproduce it locally,
Perhaps due to my machine having plenty of RAM memory? I don't really know where this comes from |
If that was a random CI failure after runner images get updated, I'd advocate disabling these tests on Windows. But since the trigger seems to be this PR, I'm worried there may be some disastrous interaction of the added feature with some strange OS settings that some users may have too (or they may have them on their github CI). In which case, are they going to have a similar problem if this PR gets merged? |
I suspect that WinIO is just broken on 9.0.2 and nothing more can be done about that. |
However it doesn't fail on my local machine 🧩, only on CI. |
If that's always only 9.0.2 , disabling the tests on Windows only on 9.0.2 seems fine to me, regardless of whether we can reproduce it locally. |
I'd prefer disabling individual tests over the whole configuration (Windows/GHC 9.0) if that's not too much trouble. But if it is, then it's fine too imo. |
My suggestion is that the validate script doesn't include this option in the GitHub CI environment. We can read environment variables just fine to take this decision. |
ae5c57e
to
c76f335
Compare
The validate script now sets |
c76f335
to
5c6e548
Compare
5c6e548
to
a307d98
Compare
a307d98
to
a562b57
Compare
I think this only works by accident:
See for example https://github.com/haskell/cabal/actions/runs/9757762049/job/26944807720?pr=10167#step:13:13. |
Otherwise CI prints `validate.sh: 332: [[: not found` and the line does nothing (but `validate.sh` continues to run), unless the system shell is `ksh` / `bash` / `zsh`. This may explain haskell#10114 (comment).
Otherwise CI prints `validate.sh: 332: [[: not found` and the line does nothing (but `validate.sh` continues to run), unless the system shell is `ksh` / `bash` / `zsh`. This may explain haskell#10114 (comment).
Otherwise CI prints `validate.sh: 332: [[: not found` and the line does nothing (but `validate.sh` continues to run), unless the system shell is `ksh` / `bash` / `zsh`. This may explain haskell#10114 (comment).
Otherwise CI prints `validate.sh: 332: [[: not found` and the line does nothing (but `validate.sh` continues to run), unless the system shell is `ksh` / `bash` / `zsh`. This may explain #10114 (comment). (cherry picked from commit 0b5cf15) # Conflicts: # validate.sh
Otherwise CI prints `validate.sh: 332: [[: not found` and the line does nothing (but `validate.sh` continues to run), unless the system shell is `ksh` / `bash` / `zsh`. This may explain #10114 (comment). (cherry picked from commit 0b5cf15)
@mergify backport 3.12 |
✅ Backports have been created
|
Use `--io-manager=native` in `lib-suite` on Windows (backport #10114)
Closes #9571