-
-
Notifications
You must be signed in to change notification settings - Fork 389
ghcide
test failures in Gentoo Linux
#3221
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
Comments
The problem is that Tasty runs test in parallel by default, and most HLS test suites do not handle this well. Set TASTY_NUM_THREADS to 1 |
Isn't the number of threads a tasty option? Could we set it explicitly in the test suites to 1 using |
That would be great |
I made an issue for this: #3245 |
Did Pepe's suggestion help? |
It seems that the I want to try to get a build environment set up that mirrors the CI exactly, hopefully get all the tests passing, then work backwards and see what is different in Gentoo compared to the CI environment (package versions, etc.) |
I cannot get the
|
Hm, it looks like I'm getting some inconsistencies with
|
I'm going to play around with the |
I'm getting a few test failures for
ghcide-1.8.0.0
when they are run with Gentoo's network-sandbox disabled (so unrelated to #3126):incomplete entries
Map
Module is symlinked
Full build log is here (raw file is ~15MB)
Your environment
GHC 9.0.2 on Gentoo Linux. All packages are installed through the system package manager.
ghcide-1.8.0.0
is being built with theghc-patched-unboxed-bytecode
flag turned OFF. (I hit other test failures when it was turned on.)Other
gentoo-haskell
-related test issues:hls-hlint-plugin
test failure in Gentoo Linux #3217hls-gadt-plugin
test failures in Gentoo Linux #3218The text was updated successfully, but these errors were encountered: