From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: bug#25774: libmicrohttpd: fails to build (test-driver aborted) Date: Fri, 17 Feb 2017 19:42:15 -0500 Message-ID: <20170218004215.GA21331@jasmine> References: <20170217154858.GD7067@sax.terramar.selidor.net> <20170217162346.4pfljt2q2vv27b6l@wasp> <20170217162934.nuetcswipdil7xje@wasp> <20170217171030.GE7067@sax.terramar.selidor.net> <20170217205341.GB26051@jasmine> <20170217235949.GA5900@sax.terramar.selidor.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58206) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cet7D-0002jc-KD for bug-guix@gnu.org; Fri, 17 Feb 2017 19:43:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cet78-0002kf-Ld for bug-guix@gnu.org; Fri, 17 Feb 2017 19:43:07 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:45747) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cet78-0002kY-Ch for bug-guix@gnu.org; Fri, 17 Feb 2017 19:43:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1cet78-0003Ob-0c for bug-guix@gnu.org; Fri, 17 Feb 2017 19:43:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <20170217235949.GA5900@sax.terramar.selidor.net> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ivan Vilata i Balaguer Cc: 25774@debbugs.gnu.org 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.