bug#22582: 25.0.90; package-test fail on w64

[Fabrice Popineau <fabrice.popineau@gmail.com>]

[-- Attachment #1.1: Type: text/plain, Size: 2977 bytes --]

Ok, closing the first part of the bug report: it is working as expected at
this point.
Two days ago, I had to debug this (require 'macro-problem) thing
and I came up with explicitly loading the libraries to make it work.

The second problem is still there. Under Windows 10 and my setup, a 10049
error is reported
when trying to connect to  http://0.0.0.0:8000/

Log file attached.

Fabrice



2016-02-07 19:02 GMT+01:00 Eli Zaretskii <eliz@gnu.org>:

> > From: Fabrice Popineau <fabrice.popineau@gmail.com>
> > Date: Sun, 7 Feb 2016 15:25:42 +0100
> >
> > The are 2 failures.
> >
> > One can be fixed simply by patching test/automated/package-test.el in
> > the following way:
> >
> > diff --git a/test/automated/package-test.el
> b/test/automated/package-test.el
> > index e10946e..e2526e3 100644
> > --- a/test/automated/package-test.el
> > +++ b/test/automated/package-test.el
> > @@ -246,12 +246,15 @@ package-test-desc-version-string
> > "Install a package which includes a dependency."
> > (with-package-test (:basedir "data/package")
> > (package-install-file (expand-file-name "macro-problem-package-1.0/"))
> > - (require 'macro-problem)
> > + (load-library "macro-aux")
> > + (load-library "macro-problem")
> > ;; `macro-problem-func' uses a macro from `macro-aux'.
> > (should (equal (macro-problem-func) '(progn a b)))
> > (package-install-file (expand-file-name "macro-problem-package-2.0/"))
> > ;; After upgrading, `macro-problem-func' depends on a new version
> > ;; of the macro from `macro-aux'.
> > + (load-library "macro-aux")
> > + (load-library "macro-problem")
> > (should (equal (macro-problem-func) '(1 b)))
> > ;; `macro-problem-10-and-90' depends on an entirely new macro from
> `macro-aux'.
> > (should (equal (macro-problem-10-and-90) '(10 90)))))
> >
> > My question is: when you ``(require 'macro-problem)'',
> > should the package mechanism be clever enough to reload the files
> > when you upgrade the package? Because clearly it doesn't happen
> > there.
> >
> > Second problem directly related to the underlying platform: the
> > connection to http://0.0.0.0:8000/ fails with a 10049 error.
> > This error is frequently reported on forums (see
> > http://www.sockets.com/err_lst1.htm for example).
> > I don't know what is the best fix.
> >
> > diff --git a/test/automated/package-test.el
> b/test/automated/package-test.el
> > index e10946e..e2526e3 100644
> > --- a/test/automated/package-test.el
> > +++ b/test/automated/package-test.el
> > @@ -374,7 +377,7 @@ package-test-desc-version-string
> > (skip-unless (not (getenv "NIX_STORE")))
> > (with-package-test (:basedir
> > package-test-data-dir
> > - :location "http://0.0.0.0:8000/")
> > + :location "http://127.0.0.1:8000/")
> > (let* ((package-menu-async t)
> > (process (start-process
> > "package-server" "package-server-buffer"
>
> Strangely enough, none of that happens to me, the test passes with
> flying colors.
>
> Can you post the full contents of your package-test.log?
>

[-- Attachment #1.2: Type: text/html, Size: 4399 bytes --]

[-- Attachment #2: package-test.log --]
[-- Type: application/octet-stream, Size: 16906 bytes --]