From: zimoun <zimon.toutoune@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: 22251@debbugs.gnu.org
Subject: bug#22251: ghc-memory test suite fails on i686
Date: Fri, 18 Dec 2020 20:40:08 +0100 [thread overview]
Message-ID: <865z4yx5rb.fsf@gmail.com> (raw)
In-Reply-To: <87bn9bptvr.fsf@netris.org> (Mark H. Weaver's message of "Sun, 27 Dec 2015 14:35:20 -0500")
Hi Mark,
This bug is very old. And probably not relevant anymore.
On Sun, 27 Dec 2015 at 14:35, Mark H Weaver <mhw@netris.org> wrote:
> The ghc-memory test suite has failed several times in a row on i686 with
> the same errors:
>
> http://hydra.gnu.org/build/893578
This build number is about openldap-2.4.46.i686-linux on
core-updates-core-updates.
With Guix f4450e8ca909530ee3432710b82f97e23acc7fef, the tests suite of
ghc-memory is turn on and the substitute seems available.
$ guix weather -s i686-linux ghc-memory
computing 1 package derivations for i686-linux...
looking for 2 store items on https://ci.guix.gnu.org...
updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
https://ci.guix.gnu.org
100.0% substitutes available (2 out of 2)
at least 0.9 MiB of nars (compressed)
3.2 MiB on disk (uncompressed)
0.130 seconds per request (0.3 seconds in total)
7.7 requests per second
at least 1,000 queued builds
i686-linux: 222 (22.2%)
armhf-linux: 287 (28.7%)
aarch64-linux: 316 (31.6%)
x86_64-linux: 173 (17.3%)
i586-gnu: 2 (.2%)
build rate: 125.58 builds per hour
x86_64-linux: 40.31 builds per hour
armhf-linux: 29.13 builds per hour
i686-linux: 33.78 builds per hour
aarch64-linux: 20.22 builds per hour
i586-gnu: 6.36 builds per hour
I am in favor to close it if no more information is added.
All the best,
simon
next prev parent reply other threads:[~2020-12-18 19:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-27 19:35 bug#22251: ghc-memory test suite fails on i686 Mark H Weaver
2020-12-18 19:40 ` zimoun [this message]
2020-12-18 22:12 ` Mark H Weaver
2020-12-18 23:05 ` zimoun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=865z4yx5rb.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=22251@debbugs.gnu.org \
--cc=mhw@netris.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).