From: "Marijn Schouten (hkBst)" <hkBst@gentoo.org>
To: bug-guile@gnu.org
Cc: guile-devel@gnu.org
Subject: Re: popen test hangs
Date: Tue, 07 Jul 2009 16:20:53 +0200 [thread overview]
Message-ID: <4A5359C5.4050105@gentoo.org> (raw)
In-Reply-To: <4A528FC5.4010006@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Marijn Schouten (hkBst) wrote:
> Neil Jerram wrote:
>> "Marijn Schouten (hkBst)" <hkBst@gentoo.org> writes:
>
>>> it seems that the popen test hangs:
>> Grrr. I thought we'd nailed that...
>
>>> then it hangs for at least an hour or so. My configure invocation is:
>>>
>>> ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu
>>> --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share
>>> --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64
>>> --disable-error-on-warning --disable-static --enable-posix --disable-networking
>>> --enable-regex --enable-deprecated --disable-elisp --enable-nls --disable-rpath
>>> --disable-debug-freelist --disable-debug-malloc --disable-guile-debug
>>> --with-threads --with-modules EMACS=no
>>>
>>> Any ideas what could be wrong or how to find out more?
>> Please look at the end of the check-guile.log file, to find out the
>> last test case that ran successfully, before the one that hung.
>
> check-guile.log ends with
>
> PASS: popen.test: open-input-pipe: no args
> PASS: popen.test: open-input-pipe: port?
> PASS: popen.test: open-input-pipe: echo hello
> PASS: popen.test: open-input-pipe: stdin==stderr
> PASS: popen.test: open-input-pipe: stdout==stderr
> PASS: popen.test: open-input-pipe: open-input-pipe process gets
> (current-input-port) as stdin
> PASS: popen.test: open-input-pipe: no duplicate
> PASS: popen.test: open-output-pipe: no args
> PASS: popen.test: open-output-pipe: port?
> PASS: popen.test: open-output-pipe: stdin==stderr
> PASS: popen.test: open-output-pipe: stdout==stderr
>
>> Then, if you like you could confirm that it is the next test that is
>> the problem, by removing everything all the other tests from
>> popen.test, and running just popen.test with
>
>> ./pre-inst-guile -s test-suite/tests/popen.test
Actually doing this allowed the tests to run perfectly. That makes it look like
it is some interaction between popen.test and the sandbox/package manager. I
will investigate further.
Thanks,
Marijn
- --
If you cannot read my mind, then listen to what I say.
Marijn Schouten (hkBst), Gentoo Lisp project, Gentoo ML
<http://www.gentoo.org/proj/en/lisp/>, #gentoo-{lisp,ml} on FreeNode
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkpTWcUACgkQp/VmCx0OL2yU0ACfeixckXA2zRbFX1ROAFvZ3xK9
0pAAoIWcDQvOMQPu+vuLxXnlrHvIjpds
=1wvz
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2009-07-07 14:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-05 21:06 GNU Guile 1.8.7 released Ludovic Courtès
2009-07-06 10:40 ` popen test hangs (was GNU Guile 1.8.7 released) Marijn Schouten (hkBst)
2009-07-06 18:25 ` popen test hangs Neil Jerram
2009-07-06 23:59 ` Marijn Schouten (hkBst)
2009-07-07 14:20 ` Marijn Schouten (hkBst) [this message]
2009-07-08 23:04 ` Neil Jerram
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=4A5359C5.4050105@gentoo.org \
--to=hkbst@gentoo.org \
--cc=bug-guile@gnu.org \
--cc=guile-devel@gnu.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).