* [core-updates-frozen] Haskell for i686-linux: report
@ 2021-12-04 9:50 zimoun
2021-12-05 16:47 ` Timothy Sample
0 siblings, 1 reply; 3+ messages in thread
From: zimoun @ 2021-12-04 9:50 UTC (permalink / raw)
To: Guix Devel
Hi,
All related Haskell packages for both x86_64 and i686 in
core-updates-frozen are not blockers for the merge. \o/
After some Cuirass monitoring and restarted some unexpected failures,
the situation for ghc-* on i686-linux is the same as the one from
current master.
Two packages are broken in core-updates-frozen and not in master:
1. ghc-ncurses
https://ci.guix.gnu.org/build/1858160/details
2. ghc-lukko
https://ci.guix.gnu.org/build/1858215/details
Therefore, ’scroll’ (because #1) and ’ganeti’ (because #2) are also
broken.
These test suite failures require some investigations. Many other ghc-*
packages too:
- ghc-sha
- ghc-validty
- ghc-bloomfilter
- ghc-tar
- ghc-llvm-hs
- ghc-lucid
https://ci.guix.gnu.org/search?query=spec%3Acore-updates-frozen+system%3Ai686-linux+status%3Afailed+ghc
Last, note that for x86_64 in core-updates-frozen, ghc-ncurses is also
broken:
https://ci.guix.gnu.org/build/1779259/details
Let merge core-updates-frozen!
Cheers,
simon
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [core-updates-frozen] Haskell for i686-linux: report
2021-12-04 9:50 [core-updates-frozen] Haskell for i686-linux: report zimoun
@ 2021-12-05 16:47 ` Timothy Sample
2021-12-07 19:06 ` bug#52357: 8 ghc-* test suite failures for i686-linux zimoun
0 siblings, 1 reply; 3+ messages in thread
From: Timothy Sample @ 2021-12-05 16:47 UTC (permalink / raw)
To: zimoun; +Cc: Guix Devel
Hi,
zimoun <zimon.toutoune@gmail.com> writes:
> After some Cuirass monitoring and restarted some unexpected failures,
> the situation for ghc-* on i686-linux is the same as the one from
> current master.
I took a few minutes to triage these. Most of them are fixable.
> Two packages are broken in core-updates-frozen and not in master:
>
> 1. ghc-ncurses
> https://ci.guix.gnu.org/build/1858160/details
Looks like this is due to an ncurses API update:
https://lists.gnu.org/archive/html/bug-ncurses/2020-08/msg00017.html
AFAICS, both scroll and ghc-ncurses are abandoned. In the case of
scroll, you could say that it’s “finished” I guess, since it’s a game.
I bet it would work fine if we drop the “KEY_EVENT” line in
“lib/UI/NCurses/Enums.chs”. Otherwise, we could consider dropping these
two packages.
> 2. ghc-lukko
> https://ci.guix.gnu.org/build/1858215/details
Upstream bug: https://github.com/haskellari/lukko/issues/15
The consensus so far is disable OFD locking on 32-bit platforms using
the “-ofd-locking” configure flag.
> These test suite failures require some investigations. Many other ghc-*
> packages too:
>
> - ghc-sha
This one is an out of memory error. Not sure what to do.
> - ghc-validty
Upstream bug: https://github.com/NorfairKing/validity/issues/84
There’s a patch there to fix the tests for 32-bit machines.
> - ghc-bloomfilter
Upstream bug: https://github.com/bos/bloomfilter/issues/7
The tests are bounds checking using an overflowed literal: 0xffffffff.
Other distros get rid of the check, but the literal could be fixed, too,
as explained in the bug report.
> - ghc-tar
Upstream bug: https://github.com/haskell/tar/issues/21 (from rekado!)
There’s no patch from upstream. It looks like a simple word size
mistake in the tests like ghc-validity or ghc-bloomfilter.
> - ghc-llvm-hs
Not sure about this one.
> - ghc-lucid
This one I’ve seen before! Upstream has trouble with nondeterministic
ordering of output HTML attributes. I guess running the tests on a
32-bit machine exposes some more of these problems. Patching the tests
to allow different orders would fix it.
[---]
It would be good to fix these, but it would be better to update our
whole Haskell stack. That’ll have to be something to attempt once c-u-f
is merged.
-- Tim
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#52357: 8 ghc-* test suite failures for i686-linux
2021-12-05 16:47 ` Timothy Sample
@ 2021-12-07 19:06 ` zimoun
0 siblings, 0 replies; 3+ messages in thread
From: zimoun @ 2021-12-07 19:06 UTC (permalink / raw)
To: 52357
Hi,
Well, it appears to me worth to track all in the bug tracker.
Initially from <https://lists.gnu.org/archive/html/guix-devel/2021-12/msg00052.html>.
---------- Forwarded message ---------
From: Timothy Sample <samplet@ngyro.com>
Date: Sun, 5 Dec 2021 at 17:47
Subject: Re: [core-updates-frozen] Haskell for i686-linux: report
> After some Cuirass monitoring and restarted some unexpected failures,
> the situation for ghc-* on i686-linux is the same as the one from
> current master.
I took a few minutes to triage these. Most of them are fixable.
> Two packages are broken in core-updates-frozen and not in master:
>
> 1. ghc-ncurses
> https://ci.guix.gnu.org/build/1858160/details
Looks like this is due to an ncurses API update:
https://lists.gnu.org/archive/html/bug-ncurses/2020-08/msg00017.html
AFAICS, both scroll and ghc-ncurses are abandoned. In the case of
scroll, you could say that it’s “finished” I guess, since it’s a game.
I bet it would work fine if we drop the “KEY_EVENT” line in
“lib/UI/NCurses/Enums.chs”. Otherwise, we could consider dropping these
two packages.
> 2. ghc-lukko
> https://ci.guix.gnu.org/build/1858215/details
Upstream bug: https://github.com/haskellari/lukko/issues/15
The consensus so far is disable OFD locking on 32-bit platforms using
the “-ofd-locking” configure flag.
> These test suite failures require some investigations. Many other ghc-*
> packages too:
>
> - ghc-sha
This one is an out of memory error. Not sure what to do.
> - ghc-validty
Upstream bug: https://github.com/NorfairKing/validity/issues/84
There’s a patch there to fix the tests for 32-bit machines.
> - ghc-bloomfilter
Upstream bug: https://github.com/bos/bloomfilter/issues/7
The tests are bounds checking using an overflowed literal: 0xffffffff.
Other distros get rid of the check, but the literal could be fixed, too,
as explained in the bug report.
> - ghc-tar
Upstream bug: https://github.com/haskell/tar/issues/21 (from rekado!)
There’s no patch from upstream. It looks like a simple word size
mistake in the tests like ghc-validity or ghc-bloomfilter.
> - ghc-llvm-hs
Not sure about this one.
> - ghc-lucid
This one I’ve seen before! Upstream has trouble with nondeterministic
ordering of output HTML attributes. I guess running the tests on a
32-bit machine exposes some more of these problems. Patching the tests
to allow different orders would fix it.
[---]
It would be good to fix these, but it would be better to update our
whole Haskell stack. That’ll have to be something to attempt once c-u-f
is merged.
-- Tim
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-12-07 19:07 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-12-04 9:50 [core-updates-frozen] Haskell for i686-linux: report zimoun
2021-12-05 16:47 ` Timothy Sample
2021-12-07 19:06 ` bug#52357: 8 ghc-* test suite failures for i686-linux zimoun
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.