GNU bug report logs -
#73312
31.0.50; textsec test failure because of UTS #46 changes
Previous Next
Reported by: Robert Pluim <rpluim <at> gmail.com>
Date: Tue, 17 Sep 2024 10:13:02 UTC
Severity: normal
Tags: fixed
Found in version 31.0.50
Fixed in version 31.1
Done: Robert Pluim <rpluim <at> gmail.com>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
> From: Robert Pluim <rpluim <at> gmail.com>
> Date: Tue, 17 Sep 2024 12:11:50 +0200
>
> Following the update to Unicode 16, the textsec tests now fail:
>
> GEN lisp/international/textsec-tests.log
> Running 12 tests (2024-09-17 11:51:51+0200, selector `(not (or (tag :unstable) (tag :nativecomp)))')
> passed 1/12 test-confusable (0.001562 sec)
> passed 2/12 test-minimal-scripts (0.000155 sec)
> passed 3/12 test-mixed-numbers (0.000846 sec)
> passed 4/12 test-resolved (0.000120 sec)
> passed 5/12 test-restriction-level (0.000259 sec)
> passed 6/12 test-scripts (0.000354 sec)
> passed 7/12 test-suspicious-email (0.001587 sec)
> passed 8/12 test-suspicious-link (0.015283 sec)
> passed 9/12 test-suspicious-local (0.000522 sec)
> passed 10/12 test-suspicious-name (0.000420 sec)
> passed 11/12 test-suspicious-url (0.000498 sec)
> Test test-suspiction-domain backtrace:
> signal(ert-test-failed (((should (textsec-domain-suspicious-p "foo/b
> ert-fail(((should (textsec-domain-suspicious-p "foo/bar.org")) :form
> (if (unwind-protect (setq value-222 (apply fn-220 args-221)) (setq f
> (let (form-description-224) (if (unwind-protect (setq value-222 (app
> (let ((value-222 'ert-form-evaluation-aborted-223)) (let (form-descr
> (let* ((fn-220 #'textsec-domain-suspicious-p) (args-221 (condition-c
> #f(lambda () [t] (let* ((fn-220 #'textsec-domain-suspicious-p) (args
> #f(compiled-function () #<bytecode -0x167cc0e1752f76aa>)()
> handler-bind-1(#f(compiled-function () #<bytecode -0x167cc0e1752f76a
> ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
> ert-run-test(#s(ert-test :name test-suspiction-domain :documentation
> ert-run-or-rerun-test(#s(ert--stats :selector ... :tests ... :test-m
> ert-run-tests((not (or (tag :unstable) (tag :nativecomp))) #f(compil
> ert-run-tests-batch((not (or (tag :unstable) (tag :nativecomp))))
> ert-run-tests-batch-and-exit((not (or (tag :unstable) (tag :nativeco
> eval((ert-run-tests-batch-and-exit '(not (or (tag :unstable) (tag :n
> command-line-1(("-L" ":." "-l" "ert" "--eval" "(setq treesit-extra-l
> command-line()
> normal-top-level()
> Test test-suspiction-domain condition:
> (ert-test-failed
> ((should (textsec-domain-suspicious-p "foo/bar.org")) :form
> (textsec-domain-suspicious-p "foo/bar.org") :value nil))
> FAILED 12/12 test-suspiction-domain (0.000228 sec) at lisp/international/textsec-tests.el:114
>
> Ran 12 tests, 11 results as expected, 1 unexpected (2024-09-17 11:51:51+0200, 0.102143 sec)
>
> 1 unexpected results:
> FAILED test-suspiction-domain
>
> This is because UTS #46 in their infinite wisdom have decided to change
> the rules on how to check what is considered an allowed character in a
> domain name. Previously, IdnaMappingTable.txt contained eg:
>
> 002F ; disallowed_STD3_valid # 1.1 SOLIDUS
>
> but now it contains
>
> 002F ; valid ; ; NV8 # 1.1 SOLIDUS
>
> with a change to section 4.1 of UTS#46 saying that only [a-z0-9-] are
> allowed for ASCII. Note that theyʼve helpfully marked
> valid-but-invalid-in-idna characters with either NV8 or XV8, but then
> have unhelpfully said that those markings are not normative. <sigh>
>
> Anyway, willfully ignoring their verbiage about normative markings,
> the following fixes it for me, at least until the next version of UTS
> #46, I guess.
Please install, and thanks.
This bug report was last modified 300 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.