all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ng0 <contact.ng0@cryptolab.net>
To: Leo Famulari <leo@famulari.name>
Cc: 25774@debbugs.gnu.org, Ivan Vilata i Balaguer <ivan@selidor.net>
Subject: bug#25774: libmicrohttpd: fails to build (test-driver aborted)
Date: Sat, 18 Feb 2017 09:51:35 +0000	[thread overview]
Message-ID: <20170218095135.hqe4r5xd3wi4on7r@wasp> (raw)
In-Reply-To: <20170218004215.GA21331@jasmine>

On 17-02-17 19:42:15, Leo Famulari wrote:
> On Sat, Feb 18, 2017 at 12:59:49AM +0100, Ivan Vilata i Balaguer wrote:
> > I think I left out a couple of lines at the end:
> > 
> > ```
> > Fatal error in GNU libmicrohttpd daemon.c:5190: MHD_stop_daemon() called while we have suspended connections.
> > 
> > FAIL test_upgrade_ssl (exit status: 134)
> > ```
> > 
> > > The only debugging suggestion I have is to make sure that your clock is
> > > correct. Test suites that do certificate verification should take care
> > > not to break in the future, but perhaps it's less common for test
> > > authors to handle the case of a clock set to the past.
> > 
> > Well, it may be some second off, but not much more than that…
> 
> That's normal. I was thinking about the clock being set to the Unix
> epoch or something extreme like that.
> 
> > 
> > > Beyond that, did you find anything relevant on the upstream bug tracker?
> > > 
> > > https://ng.gnunet.org/bugs/view_all_bug_page.php
> > 
> > I can't find anything related there, I also searched the net before
> > sending the report but found nothing that seemed the same error.
> 
> What about this one?
> 
> https://ng.gnunet.org/bugs/view.php?id=4844
> 
> The report says that it's limited to ppc64le, but the symptoms appear
> identical.
> 
> 
> 

I could ask grothoff about if a new release will happen soon, but it
looks like it:

commit f154b0ef8894185fd6c01888d10280049bed10c6
Author: Christian Grothoff <christian@grothoff.org>
Date:   Wed Feb 15 13:38:06 2017 +0100

    bump dates and versions and update ChangeLog


This is the HEAD~~ commit.
The one afterwards fixes an android problem.
-- 
ng0 -- https://www.inventati.org/patternsinthechaos/

  parent reply	other threads:[~2017-02-18  9:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-17 15:48 bug#25774: libmicrohttpd: fails to build (test-driver aborted) Ivan Vilata i Balaguer
2017-02-17 16:23 ` ng0
2017-02-17 16:29   ` ng0
2017-02-17 17:10     ` Ivan Vilata i Balaguer
2017-02-17 17:23       ` ng0
2017-02-17 20:53       ` Leo Famulari
2017-02-17 23:59         ` Ivan Vilata i Balaguer
2017-02-18  0:42           ` Leo Famulari
2017-02-18  1:18             ` Ivan Vilata i Balaguer
2017-02-18  9:51             ` ng0 [this message]
2017-02-20 11:08               ` Ivan Vilata i Balaguer
2017-03-05 22:15 ` bug#25774: Resolved ng0

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

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

  git send-email \
    --in-reply-to=20170218095135.hqe4r5xd3wi4on7r@wasp \
    --to=contact.ng0@cryptolab.net \
    --cc=25774@debbugs.gnu.org \
    --cc=ivan@selidor.net \
    --cc=leo@famulari.name \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.