GNU bug report logs - #28545
25.2; package-test-update-archives-async sometimes fails

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 28545 in the body.
You can then email your comments to 28545 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: "Leo Silva (a.k.a kirotawa)" <kirotawa <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: Error in build for Debian - emacs25-25.2+1
Date: Thu, 21 Sep 2017 16:56:25 -0300

Hi,

I'm trying to build emacs25-25.2+1 and facing this issue in build time
[1]. I'm not familiar with lisp but any clue in why it's happen would
be helpful. I'm running this through a schroot.


[1]
Test package-test-update-archives-async condition:
    (error "Error retrieving: http://0.0.0.0:8000/archive-contents
(error connection-failed \"failed with code 111
\" :host \"0.0.0.0\" :service 8000)")
   FAILED  17/20  package-test-update-archives-async
Package refresh done
Package menu: Operation started [Installing 1]
Setting `package-selected-packages' temporarily since "emacs -q" would
overwrite customizations
Generating autoloads for simple-single.el...
Generating autoloads for simple-single.el...done

Checking /tmp/pkg-test-user-dir-27763TKN/simple-single-1.3...
Compiling /tmp/pkg-test-user-dir-27763TKN/simple-single-1.3/simple-single-autoloads.el...
Compiling /tmp/pkg-test-user-dir-27763TKN/simple-single-1.3/simple-single-pkg.el...
Compiling /tmp/pkg-test-user-dir-27763TKN/simple-single-1.3/simple-single.el...
Done (Total of 1 file compiled, 2 skipped)
Package menu: Operation finished [Installed 1]
   passed  18/20  package-test-update-listing
   passed  19/20  package-x-test-upload-buffer
   passed  20/20  package-x-test-upload-new-version

Ran 20 tests, 19 results as expected, 1 unexpected (2017-09-21 16:32:37-0300)

1 unexpected results:
   FAILED  package-test-update-archives-async

ERROR: package-test.log

Message #8 received at 28545 <at> debbugs.gnu.org (full text, mbox):

From: Glenn Morris <rgm <at> gnu.org>
To: "Leo Silva \(a.k.a kirotawa\)" <kirotawa <at> gmail.com>
Cc: 28545 <at> debbugs.gnu.org
Subject: Re: bug#28545: Error in build for Debian - emacs25-25.2+1
Date: Fri, 22 Sep 2017 11:51:51 -0400

"Leo Silva (a.k.a kirotawa)" wrote:

> I'm trying to build emacs25-25.2+1 and facing this issue in build time
[...]
> Test package-test-update-archives-async condition:
>     (error "Error retrieving: http://0.0.0.0:8000/archive-contents
> (error connection-failed \"failed with code 111
> \" :host \"0.0.0.0\" :service 8000)")
>    FAILED  17/20  package-test-update-archives-async

So, you've succesfully built Emacs, and a single (?) test is failing.
I'd suggest you just ignore the test failure. This test starts an
external process using python to listen on a local address, and in my
experience it not infrequently fails to start properly. I think the
failure is probably unrelated to Emacs.

Message #17 received at 28545-done <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefan <at> marxist.se>
To: Glenn Morris <rgm <at> gnu.org>
Cc: 28545-done <at> debbugs.gnu.org,
 "Leo Silva \(a.k.a kirotawa\)" <kirotawa <at> gmail.com>
Subject: Re: bug#28545: Error in build for Debian - emacs25-25.2+1
Date: Sun, 29 Sep 2019 03:01:06 +0200

Glenn Morris <rgm <at> gnu.org> writes:

> "Leo Silva (a.k.a kirotawa)" wrote:
>
>> I'm trying to build emacs25-25.2+1 and facing this issue in build time
> [...]
>> Test package-test-update-archives-async condition:
>>     (error "Error retrieving: http://0.0.0.0:8000/archive-contents
>> (error connection-failed \"failed with code 111
>> \" :host \"0.0.0.0\" :service 8000)")
>>    FAILED  17/20  package-test-update-archives-async
>
> So, you've succesfully built Emacs, and a single (?) test is failing.
> I'd suggest you just ignore the test failure. This test starts an
> external process using python to listen on a local address, and in my
> experience it not infrequently fails to start properly. I think the
> failure is probably unrelated to Emacs.

According to the above, this is probably not a bug in Emacs.  I'm
therefore closing this bug report.

If that's incorrect, please reopen.

Best regards,
Stefan Kangas

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.