mono-traversable: tests hang on 32-bit architectures #210
Comments
|
The same thing seems to be happening for classy-prelude, too. |
hololeap
added a commit
to hololeap/gentoo-haskell
that referenced
this issue
May 6, 2023
x86 is mostly untested, and even building a subset of ::haskell revealed failing tests which pass on amd64. With the new behavior of hackport to only add ARCH to KEYWORDS, there will be CI failures if a package has ~x86 removed but not from its revdep tree as well. The only sensible mitigation is to remove ~x86 tree-wide until we have a dedicated tester willing to fix current bugs. See: snoyberg/mono-traversable#210 Signed-off-by: hololeap <[email protected]>
hololeap
added a commit
to gentoo-haskell/gentoo-haskell
that referenced
this issue
May 6, 2023
x86 is mostly untested, and even building a subset of ::haskell revealed failing tests which pass on amd64. With the new behavior of hackport to only add ARCH to KEYWORDS, there will be CI failures if a package has ~x86 removed but not from its revdep tree as well. The only sensible mitigation is to remove ~x86 tree-wide until we have a dedicated tester willing to fix current bugs. See: snoyberg/mono-traversable#210 Signed-off-by: hololeap <[email protected]>
|
@swt2c I have just updated the ci and I would like to have a check for the issue you are running into. Could you add what containers you would like to have this build on? A possible good template is from bytestring's ci.yaml |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Over in Debian, we're seeing the unit tests for mono-traversable 1.0.15.3 hang on all 32-bit architectures (armel, armhf, i386, etc.) with GHC 9.0.2. Unfortunately, the tests just get stuck and don't produce any useful output (and the build process gets killed for producing no output for 150 minutes:
The text was updated successfully, but these errors were encountered: