GNU bug report logs -
#32671
00-repl-server.test fails sometimes
Previous Next
To reply to this bug, email your comments to 32671 AT debbugs.gnu.org.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guile <at> gnu.org
:
bug#32671
; Package
guile
.
(Sun, 09 Sep 2018 13:18:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
"pelzflorian (Florian Pelz)" <pelzflorian <at> pelzflorian.de>
:
New bug report received and forwarded. Copy sent to
bug-guile <at> gnu.org
.
(Sun, 09 Sep 2018 13:18:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
I get the following error 3 in 7 times when building Guile 2.2.4 on
Guix on Debian Buster on my Beaglebone Black (armhf architecture):
PASS: repl-server: simple expression
ERROR: repl-server: HTTP inter-protocol attack - arguments: ((system-error "fport_write" "~A" ("Datenübergabe unterbrochen (broken pipe)") (32)))
Find attached the corresponding strace created by running:
$ export GUILE_LOAD_PATH=test-suite
$ strace ./libguile/guile test-suite/tests/00-repl-server.test
Note that the test does not fail reliably but only sometimes.
Regards,
Florian
[err (text/plain, attachment)]
Information forwarded
to
bug-guile <at> gnu.org
:
bug#32671
; Package
guile
.
(Wed, 15 Jan 2025 17:08:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 32671 <at> debbugs.gnu.org (full text, mbox):
"pelzflorian (Florian Pelz)" <pelzflorian <at> pelzflorian.de> writes:
> I get the following error 3 in 7 times when building Guile 2.2.4 on
> Guix on Debian Buster on my Beaglebone Black (armhf architecture):
>
> PASS: repl-server: simple expression
> ERROR: repl-server: HTTP inter-protocol attack - arguments: ((system-error "fport_write" "~A" ("Datenübergabe unterbrochen (broken pipe)") (32)))
[...]
> Note that the test does not fail reliably but only sometimes.
I've seen the same thing, and I had a suspicion that they mostly (only?)
happen during parallel testing, e.g. "make -j5 check". That suspicion
was reinforced when I was able to reproduce the error more relably via a
few moreutils parallel runs like this:
$ parallel -j 3 ./check-guile \
-- 00-repl-server.test 00-repl-server.test \
I found that the failure is due to a throw from write request and
wrapping it like this:
;; Simulate an HTTP inter-protocol attack.
(catch 'system-error
(lambda ()
(write-request (build-request (string->uri "http://localhost"))
socket))
(lambda what
(format (current-error-port) "write-request exception ~s\n" what)
(throw 'unresolved what)))
does suppress the failure, while writing the same exception list seen in
the original failures to stderr.
I haven't actually looked closely at the test to see what the failure
might mean.
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
This bug report was last modified 148 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.