From: Rob Browning <rlb@defaultvalue.org>
To: "david@lisle.ca" <david@lisle.ca>, 34691@debbugs.gnu.org
Subject: bug#34691: Guile 2.2.4 make check failure
Date: Thu, 15 Jul 2021 21:29:31 -0500 [thread overview]
Message-ID: <87wnprat4k.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <314733374.1104980.1551398310834@sitemailxchange.domainpeople.com>
David Lisle <david@lisle.ca> writes:
> FAIL: test-out-of-memory
Thanks for the report -- for what it's worth, in Debian at least we've
marked that one as unreliable:
https://salsa.debian.org/rlb/deb-guile/-/blob/f24ab0150132d906b9724128576c36c39361cab7/debian/patches/0005-Mark-test-out-of-memory-as-an-expected-failure-for-n.patch
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
prev parent reply other threads:[~2021-07-16 2:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 23:58 bug#34691: Guile 2.2.4 make check failure David Lisle
2021-07-16 2:29 ` Rob Browning [this message]
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wnprat4k.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=34691@debbugs.gnu.org \
--cc=david@lisle.ca \
/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.
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).