From: Rob Browning <rlb@defaultvalue.org>
To: 31776@debbugs.gnu.org
Cc: Emilio Pozuelo Monfort <pochu@debian.org>,
900652@bugs.debian.org, 900652-forwarded@bugs.debian.org
Subject: bug#31776: guile-2.2: FTBFS on armhf: FAIL: gc.test: gc: after-gc-hook gets called
Date: Sat, 16 Jun 2018 17:07:05 -0500 [thread overview]
Message-ID: <87muvuwfli.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <874liar1ic.fsf@trouble.defaultvalue.org>
Rob Browning <rlb@defaultvalue.org> writes:
> It looks like gc.test may be failing intermittently in Debian (see below).
> Searching around I saw at least one other report of this in the #guile
> logs from last year.
>
> For now, I'm wondering if if would be plausible to mark the test as
> unresolved to avoid guile-2.2's removal from Debian testing, or if the
> failure is likely to indicate a problem serious enough to warrant that
> removal.
Just wanted to check back about this. It's caused a build on the buildds
to fail again.
Thanks
--
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
next prev parent reply other threads:[~2018-06-16 22:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <152796556058.30262.13172727695488534983.reportbug@tatooine>
2018-06-10 17:32 ` bug#31776: guile-2.2: FTBFS on armhf: FAIL: gc.test: gc: after-gc-hook gets called Rob Browning
2018-06-16 22:07 ` Rob Browning [this message]
2018-07-19 16:16 ` Rob Browning
[not found] ` <878t67td3t.fsf@trouble.defaultvalue.org>
2018-08-06 13:20 ` Göran Weinholt
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=87muvuwfli.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=31776@debbugs.gnu.org \
--cc=900652-forwarded@bugs.debian.org \
--cc=900652@bugs.debian.org \
--cc=pochu@debian.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.
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).