Subject: Re: bug#54348: Guile 3.0.7 fails to build on armhf-linux
From: Ludovic Courtès <[email-masked]>
To: [email-masked]
Date: Tue, 15 Mar 2022 14:40:52 +0100
List-Id: <debbugs-submit.debbugs.gnu.org>

Hi,

Ludovic Courtès <[email-masked]> skribis:

> Guile 3.0.7 appears to fail tests reproducibly on armhf-linux:
>
> Running vm.test
> Running weaks.test
> Running web-client.test
> Running web-http.test
> Running web-request.test
> Running web-response.test
> Running web-server.test
> ERROR: web-server.test: GET / - arguments: ((system-error "connect" "~A" ("Connection refused") (111)))
> ERROR: web-server.test: GET /latin1 - arguments: ((system-error "connect" "~A" ("Connection refused") (111)))
> ERROR: web-server.test: GET /user-agent - arguments: ((system-error "connect" "~A" ("Connection refused") (111)))
> ERROR: web-server.test: GET /does-not-exist - arguments: ((system-error "connect" "~A" ("Connection refused") (111)))
> ERROR: web-server.test: GET with keep-alive - arguments: ((system-error "connect" "~A" ("Connection refused") (111)))
> ERROR: web-server.test: POST / - arguments: ((system-error "connect" "~A" ("Connection refused") (111)))

Well, as it turns out it’s not 100% reproducible after all.  Probably a
timing issue.  I was unable to reproduce it on overdrive1.guix anyway,
so now ci.guix has substitutes for (@@ (gnu packages commencement)
guile-final) for armhf-linux.

Looking at ‘web-server.test’, there’s no synchronization between HTTP
server startup and the first test; thus, there’s a possibility that the
HTTP server is not listening yet by the time the main thread attempts to
connect to the server.  Fixed upstream:

  https://git.savannah.gnu.org/cgit/guile.git/commit/?id=f18f67022314eefced887df0a470a440f70f592c

Ludo’.