emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] Release 9.0.5


From: Fabrice Popineau
Subject: Re: [O] Release 9.0.5
Date: Sat, 11 Feb 2017 16:37:02 +0100

Thanks Nicolas for the confirmation.

I am running Emacs 25.2rc2 under Windows 10 compiled with Mingw64.
2 of the failures seem to be harmless.

This one is about the file system which behaves differently under Windows :

F test-org-export/file-uri
    Test ‘org-export-file-uri’ specifications.
    (ert-test-failed
     ((should
       (equal "file:///local.org"
     (org-export-file-uri "/local.org")))
      :form
      (equal "file:///local.org" "file://d:/local.org")
      :value nil :explanation
      (arrays-of-different-length 17 19 "file:///local.org" "file://d:/local.org" first-mismatch-at 7)))

The absolute path has the drive name. So actually not a failure.

F test-org-pcomplete/keyword
    Test keyword and block completion.
    (ert-test-failed
     ((should
       (equal "#+startup: "
     (org-test-with-temp-text "#+start<point>"
(pcomplete)
(buffer-string))))
      :form
      (equal "#+startup: " "#+STARTUP: ")
      :value nil :explanation
      (array-elt 2
(different-atoms
 (115 "#x73" "?s")
 (83 "#x53" "?S")))))

This one is because pcomplete is used to get completion, and the completion depends on
the pcomplete-ignore-case variable, which makes pcomplete ignore case for
windows-nt and cygwin by default.

The last one is strange:

F test-org-element/link-parser
    Test ‘link’ parser.
    (ert-test-failed
     ((should
       (equal "id"
     (org-test-with-temp-text "[[id:aaaa]]"
(org-element-property :type ...))))
      :form
      (equal "id" "fuzzy")
      :value nil :explanation
      (arrays-of-different-length 2 5 "id" "fuzzy" first-mismatch-at 0)))

This is complete non sense, because when I evaluate the test form, I actually get "id" and I have
no idea where this "fuzzy" may come from. 

Do you also get a warning like this:
Making org-entities-user local to  *temp*-443480 while let-bound!
in the *Messages* buffer ?

Fabrice

2017-02-11 1:47 GMT+01:00 Nicolas Goaziou <address@hidden>:
Hello,

Fabrice Popineau <address@hidden> writes:

> Sorry for the noise.
> I found the culprit and it was on my side.
> Everything is working again
> but there are still 3 unexpected failures to the tests.

FWIW, i cannot reproduce it. Neither can the BuildBot.

Regards,

--
Nicolas Goaziou



--
Fabrice Popineau
-----------------------------
SUPELEC
Département Informatique
3, rue Joliot Curie
91192 Gif/Yvette Cedex
Tel direct : +33 (0) 169851950
Standard : +33 (0) 169851212
------------------------------


reply via email to

[Prev in Thread] Current Thread [Next in Thread]