* popen test hangs (was GNU Guile 1.8.7 released) [not found] <87k52mn8kb.fsf@gnu.org> @ 2009-07-06 10:40 ` Marijn Schouten (hkBst) 2009-07-06 18:25 ` popen test hangs Neil Jerram 0 siblings, 1 reply; 5+ messages in thread From: Marijn Schouten (hkBst) @ 2009-07-06 10:40 UTC (permalink / raw) To: bug-guile; +Cc: guile-devel -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ludovic � wrote: > We are pleased to announce GNU Guile release 1.8.7. Hi, it seems that the popen test hangs: ;;; (foo-pws) Running exceptions.test Running filesys.test Running format.test Running fractions.test Running ftw.test Running gc.test Running getopt-long.test Running goops.test Running guardians.test Running hash.test Running hooks.test Running import.test Running interp.test Running list.test Running load.test Running modules.test Running numbers.test Running optargs.test Running options.test Running poe.test Running popen.test 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? 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 iEYEARECAAYFAkpR1LoACgkQp/VmCx0OL2y9FACgyQwm21xm2B40mnTi26ravgnl rPgAoL9cnTKQ9vT6DGrxEZKcm7qqp56K =m4+J -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: popen test hangs 2009-07-06 10:40 ` popen test hangs (was GNU Guile 1.8.7 released) Marijn Schouten (hkBst) @ 2009-07-06 18:25 ` Neil Jerram 2009-07-06 23:59 ` Marijn Schouten (hkBst) 0 siblings, 1 reply; 5+ messages in thread From: Neil Jerram @ 2009-07-06 18:25 UTC (permalink / raw) To: Marijn Schouten (hkBst); +Cc: bug-guile, guile-devel "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. 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 Then, if possible, add debugging (display ...) lines, use GDB, etc., to try to find out more about the hang. Thanks! Neil ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: popen test hangs 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) 0 siblings, 1 reply; 5+ messages in thread From: Marijn Schouten (hkBst) @ 2009-07-06 23:59 UTC (permalink / raw) To: Neil Jerram; +Cc: bug-guile, guile-devel -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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 > > Then, if possible, add debugging (display ...) lines, use GDB, etc., > to try to find out more about the hang. > > Thanks! > Neil - -- 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 iEYEARECAAYFAkpSj8UACgkQp/VmCx0OL2xLWACfbCptX75eveVg5A3Hf5d49sp/ W9sAmQGrkBh5ytzzL4jbLXVmZEWml97U =VaKC -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: popen test hangs 2009-07-06 23:59 ` Marijn Schouten (hkBst) @ 2009-07-07 14:20 ` Marijn Schouten (hkBst) 2009-07-08 23:04 ` Neil Jerram 0 siblings, 1 reply; 5+ messages in thread From: Marijn Schouten (hkBst) @ 2009-07-07 14:20 UTC (permalink / raw) To: bug-guile; +Cc: guile-devel -----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----- ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: popen test hangs 2009-07-07 14:20 ` Marijn Schouten (hkBst) @ 2009-07-08 23:04 ` Neil Jerram 0 siblings, 0 replies; 5+ messages in thread From: Neil Jerram @ 2009-07-08 23:04 UTC (permalink / raw) To: Marijn Schouten (hkBst); +Cc: bug-guile, guile-devel "Marijn Schouten (hkBst)" <hkBst@gentoo.org> writes: >> 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 Thanks, that indicates this test: (pass-if "open-input-pipe process gets (current-input-port) as stdin" (let* ((p2c (pipe)) (port (with-input-from-port (car p2c) (lambda () (open-input-pipe "read line && echo $line"))))) (display "hello\n" (cdr p2c)) (force-output (cdr p2c)) (let ((result (eq? (read port) 'hello))) (close-port (cdr p2c)) (close-pipe port) result))) We had trouble with this one because of different shells. The open-input-pipe line was originally "read && echo $REPLY", but that didn't work in Dash, so we changed it to "read line && echo $line" as shown above. Is it possible that your sandbox/package manager uses a different shell from what is used when you run >>> ./pre-inst-guile -s test-suite/tests/popen.test by hand, and that "read line && echo $line" doesn't work in the sandbox/package manager shell? Thanks, Neil ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2009-07-08 23:04 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <87k52mn8kb.fsf@gnu.org>
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)
2009-07-08 23:04 ` Neil Jerram
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).