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
:form
: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