From: "Göran Weinholt" <goran@weinholt.se>
To: Rob Browning <rlb@defaultvalue.org>
Cc: Emilio Pozuelo Monfort <pochu@debian.org>,
900652-forwarded@bugs.debian.org, guile-devel@gnu.org,
31776@debbugs.gnu.org
Subject: bug#31776: guile-2.2: FTBFS on armhf: FAIL: gc.test: gc: after-gc-hook gets called
Date: Mon, 06 Aug 2018 15:20:32 +0200 [thread overview]
Message-ID: <87mutz4onz.fsf__5317.35140034488$1533561612$gmane$org@teapot.weinholt.se> (raw)
In-Reply-To: <878t67td3t.fsf@trouble.defaultvalue.org> (Rob Browning's message of "Thu, 19 Jul 2018 11:16:38 -0500")
[-- Attachment #1: Type: text/plain, Size: 2012 bytes --]
Rob Browning <rlb@defaultvalue.org> writes:
> Rob Browning <rlb@defaultvalue.org> writes:
>
>> 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.
>
> As an update, If we don't resolve this, guile-2.2 will be removed from
> Debian testing this weekend.
Hello Rob,
The test fails with 2.2.4+1-1 on amd64 as well:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/guile-2.2.html
It's really tricky to get it to fail predictably, but you can even your
odds by testing only asyncs.test and gc.test:
apt-get source guile-2.2
cd guile-2.2-2.2.4+1
dpkg-buildpackage -us -uc
mkdir test-suite/async-tests
cp test-suite/tests/{asyncs,gc}.test test-suite/async-tests/
meta/guile --debug -L $PWD/test-suite --no-auto-compile \
-e main -s $PWD/test-suite/guile-test \
--test-suite $PWD/test-suite/async-tests \
--log-file check-guile-async.log
Try the last command around a dozen times and it'll fail eventually.
I didn't get further with debugging than determining that something
probably goes wrong in the interaction between queue_after_gc_hook(),
scm_i_async_push() and scm_i_async_pop(). Every time there was a
failure, this condition was false (the cdr was set to empty list):
if (scm_is_false (SCM_CDR (after_gc_async_cell)))
{
SCM_SETCDR (after_gc_async_cell, t->pending_asyncs);
t->pending_asyncs = after_gc_async_cell;
}
Regards,
--
Göran Weinholt
Debian developer
73 de SA6CJK
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2018-08-06 13:20 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
2018-07-19 16:16 ` Rob Browning
[not found] ` <878t67td3t.fsf@trouble.defaultvalue.org>
2018-08-06 13:20 ` Göran Weinholt [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='87mutz4onz.fsf__5317.35140034488$1533561612$gmane$org@teapot.weinholt.se' \
--to=goran@weinholt.se \
--cc=31776@debbugs.gnu.org \
--cc=900652-forwarded@bugs.debian.org \
--cc=guile-devel@gnu.org \
--cc=pochu@debian.org \
--cc=rlb@defaultvalue.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).