unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: rennes@openmailbox.org
Cc: guix-devel@gnu.org, 25463@debbugs.gnu.org
Subject: Re: bug#25463: guile-2.0.13 Check errors
Date: Sat, 11 Feb 2017 22:03:36 +0100	[thread overview]
Message-ID: <87vasg1luf.fsf@gnu.org> (raw)
In-Reply-To: <4f693f6528e76a93e17e73450e2bc320@openmailbox.org> (rennes@openmailbox.org's message of "Mon, 16 Jan 2017 19:25:35 -0600")

Hello!

rennes@openmailbox.org skribis:

> I am trying to build guile version 2.0.13 in GNU Hurd through Guix
> package manager, in the 'Check' phase I have 4 errors; I am attaching
> the build log(config.zip), environment
> variables(environment-variables) and test log(check-guile.zip).
>
> This is a grep of errors, any idea how I can deal with this?
>
> /*---------------------------------------------------------------------------------*/
> ERROR: 00-repl-server.test: repl-server: simple expression -
> arguments: ((system-error "fport_fill_input" "~A" ("Transport endpoint
> is not connected") (1073741881)))
> ERROR: 00-repl-server.test: repl-server: HTTP inter-protocol attack - 
> arguments: ((system-error "fport_fill_input" "~A" ("Transport endpoint
> is not connected") (1073741881)))

The Guix package for Guile incorporates a patch that corresponds to
Guile commit 2fbde7f02adb8c6585e9baf6e293ee49cd23d4c4, which fixes a
race condition for these tests.

Could you check that this patch is really being used?

> ERROR: statprof.test: return values - arguments: ((system-error
> "setitimer" "~A" ("Function not implemented") (1073741902)))
> ERROR: statprof.test: statistical sample counts within expected range
> - 
> arguments: ((misc-error #f "~A" ("Can't reset profiler while profiler
> is running.") #f))
> ERROR: statprof.test: accurate call counting - arguments: ((misc-error
> #f "~A" ("Can't reset profiler while profiler is running.") #f))

This file uses a ‘when-implemented’ macro to skip tests upon ENOSYS
(“Function not implemented”).

The first of these 3 tests lacked it though, so I’ve added it in commit
f2764cb1031379c47a17c02fef3f8164a6ce9cda.

Could you run these tests manually to see what’s going on?  From the
top-level build tree of Guile, run:

  ./check-guile statprof.test

and see if it fails similarly.  If it does, you can add ‘display’ or
‘pk’ calls in the tests to see what’s going on.

HTH!

Ludo’.

  reply	other threads:[~2017-02-11 21:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-17  1:25 guile-2.0.13 Check errors rennes
2017-02-11 21:03 ` Ludovic Courtès [this message]
2017-02-12  8:37   ` bug#25463: " rennes
2017-02-12 13:44     ` Manolis Ragkousis
2017-02-12 21:18       ` Ludovic Courtès
2017-02-13  9:47         ` Richard Braun
2017-02-19 15:53   ` Manolis Ragkousis
2017-03-06 16:00     ` Ludovic Courtès
2017-03-06 16:45       ` Manolis Ragkousis
2017-03-06 22:53         ` Ludovic Courtès

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vasg1luf.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=25463@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=rennes@openmailbox.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).