guile-3.0.7: suspendable-ports.test: test case fails

  • Open
  • quality assurance status badge
Details
2 participants
  • Maxime Devos
  • Ryan Sundberg
Owner
unassigned
Submitted by
Ryan Sundberg
Severity
normal
R
R
Ryan Sundberg wrote on 22 Sep 2021 06:00
(address . bug-guix@gnu.org)
8257407a-0bc7-b6f0-478a-2bac7a9815d6@arctype.co
This test case is consistently failing on my machine when building guile:

./pre-inst-env guix build guile

...
Running suspendable-ports.test
UNRESOLVED: suspendable-ports.test: non-revealed port is closed
ERROR: suspendable-ports.test: revealed port fdes not closed -
arguments: ((system-error "seek" "~A" ("Bad file descriptor") (9)))

Totals for this test run:
passes: 42439
failures: 0
unexpected passes: 0
expected failures: 10
unresolved test cases: 554
untested test cases: 1
unsupported test cases: 1
errors: 1

Kernel: Linux bb11 5.14.3 #1 SMP 1 x86_64 GNU/Linux

Guix commit: c4b7bcc2569e40c6b925bc9e8fde01c5744c29f7

Log file attached.

--
Sincerely,
Ryan Sundberg
Attachment: OpenPGP_signature
M
M
Maxime Devos wrote on 22 Sep 2021 20:07
41910c7d62a873bbddd58cc71e38084e24a6dced.camel@telenet.be
Ryan Sundberg via Bug reports for GNU Guix schreef op di 21-09-2021 om 21:00 [-0700]:
Toggle quote (10 lines)
> This test case is consistently failing on my machine when building guile:
>
> ./pre-inst-env guix build guile
>
> ...
> Running suspendable-ports.test
> UNRESOLVED: suspendable-ports.test: non-revealed port is closed
> ERROR: suspendable-ports.test: revealed port fdes not closed -
> arguments: ((system-error "seek" "~A" ("Bad file descriptor") (9)))

-----BEGIN PGP SIGNATURE-----

iI0EABYKADUWIQTB8z7iDFKP233XAR9J4+4iGRcl7gUCYUtw5BccbWF4aW1lZGV2
b3NAdGVsZW5ldC5iZQAKCRBJ4+4iGRcl7oSaAQCxgrAvEAhsPCWfqmz+oXGS33Hy
l7EXUHefThG7Stax2wEAvIMpu/DiKCBt/InOcpyx4GqHZZHnlLA8Y8EXCPG86QQ=
=d0ks
-----END PGP SIGNATURE-----


?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 50729@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 50729
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch