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

Bug#1052966: rainbow-delimiters: FTBFS: make: *** [debian/rules:4: binary] Error 25



Source: rainbow-delimiters
Version: 2.1.5-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lucas@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with elpa
>    dh_update_autotools_config
>    dh_autoreconf
>    dh_elpa_test
> 	emacs -batch -Q -l package --eval "(add-to-list 'package-directory-list \"/usr/share/emacs/site-lisp/elpa\")" --eval "(add-to-list 'package-directory-list \"/usr/share/emacs/site-lisp/elpa-src\")" -f package-initialize -L . -l rainbow-delimiters-test.el --eval \(ert-run-tests-batch-and-exit\)
> Running 24 tests (2023-09-26 06:54:26+0000, selector ‘t’)
>    passed   1/24  can-customize-face-picker (0.000448 sec)
>    passed   2/24  can-disable-mode (0.000060 sec)
>    passed   3/24  can-enable-mode (0.000042 sec)
>    passed   4/24  cycles-faces (0.000152 sec)
>    passed   5/24  delimiters-disabled-by-face-picker-contribute-to-depth (0.000098 sec)
>    passed   6/24  doesnt-cycle-outermost-only-faces (0.000130 sec)
>    passed   7/24  doesnt-highlight-escaped-delimiters (0.000213 sec)
>    passed   8/24  doesnt-highlight-in-comments-1 (0.000250 sec)
>    passed   9/24  doesnt-highlight-in-comments-2 (0.002313 sec)
>    passed  10/24  doesnt-highlight-in-strings (0.000266 sec)
>    passed  11/24  doesnt-higlight-nondelimiters-1 (0.000091 sec)
>    passed  12/24  doesnt-higlight-nondelimiters-2 (0.000202 sec)
>    passed  13/24  face-picker-can-disable-highlighting (0.000127 sec)
> Test highlights-all-delimiters backtrace:
>   signal(ert-test-failed (((should (ert-equal-including-properties (pr
>   ert-fail(((should (ert-equal-including-properties (progn (remove-lis
>   (if (unwind-protect (setq value-46 (apply fn-44 args-45)) (setq form
>   (let (form-description-48) (if (unwind-protect (setq value-46 (apply
>   (let ((value-46 'ert-form-evaluation-aborted-47)) (let (form-descrip
>   (let* ((fn-44 #'ert-equal-including-properties) (args-45 (condition-
>   (let ((str "foo<int> x;")) (insert str) (fontify-buffer) (let* ((fn-
>   (progn (funcall 'c++-mode) (font-lock-mode) (rainbow-delimiters-mode
>   (unwind-protect (progn (funcall 'c++-mode) (font-lock-mode) (rainbow
>   (save-current-buffer (set-buffer temp-buffer) (unwind-protect (progn
>   (let ((temp-buffer (generate-new-buffer " *temp*" t))) (save-current
>   (lambda nil (let ((temp-buffer (generate-new-buffer " *temp*" t))) (
>   ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
>   ert-run-test(#s(ert-test :name highlights-all-delimiters :documentat
>   ert-run-or-rerun-test(#s(ert--stats :selector t :tests ... :test-map
>   ert-run-tests(t #f(compiled-function (event-type &rest event-args) #
>   ert-run-tests-batch(nil)
>   ert-run-tests-batch-and-exit()
>   command-line-1(("-l" "package" "--eval" "(add-to-list 'package-direc
>   command-line()
>   normal-top-level()
> Test highlights-all-delimiters condition:
>     (ert-test-failed
>      ((should
>        (ert-equal-including-properties
> 	(progn ... ...)
> 	#("foo<int> x;" 0 3 ... 3 4 ... 4 7 ... 7 8 ... 9 10 ...)))
>       :form
>       (ert-equal-including-properties
>        #("foo<int> x;" 0 3
> 	 (face font-lock-type-face)
> 	 3 4
> 	 (face ... c-<>-c-types-set t)
> 	 4 7
> 	 (face font-lock-type-face)
> 	 7 8
> 	 (face ...)
> 	 9 10
> 	 (face font-lock-variable-name-face))
>        #("foo<int> x;" 0 3
> 	 (face font-lock-type-face)
> 	 3 4
> 	 (face ...)
> 	 4 7
> 	 (face font-lock-type-face)
> 	 7 8
> 	 (face ...)
> 	 9 10
> 	 (face font-lock-variable-name-face)))
>       :value nil :explanation
>       (char 3 "<"
> 	    (different-properties-for-key c-<>-c-types-set
> 					  (different-atoms t nil))
> 	    context-before "foo" context-after "int> x;")))
>    FAILED  14/24  highlights-all-delimiters (0.048558 sec) at rainbow-delimiters-test.el:144
>    passed  15/24  highlights-already-highlighted (0.004625 sec)
>    passed  16/24  highlights-matching-braces (0.000125 sec)
>    passed  17/24  highlights-matching-brackets (0.000100 sec)
>    passed  18/24  highlights-matching-parens (0.000096 sec)
>    passed  19/24  highlights-mismatched (0.000214 sec)
>    passed  20/24  highlights-mixed-matching-delimiters (0.000139 sec)
>    passed  21/24  highlights-nested-matching-braces (0.000125 sec)
>    passed  22/24  highlights-nested-matching-brackets (0.000134 sec)
>    passed  23/24  highlights-nested-matching-parens (0.000158 sec)
>    passed  24/24  highlights-unmatched (0.000160 sec)
> 
> Ran 24 tests, 23 results as expected, 1 unexpected (2023-09-26 06:54:26+0000, 0.150620 sec)
> 
> 1 unexpected results:
>    FAILED  highlights-all-delimiters
> 
> dh_elpa_test: error: emacs -batch -Q -l package --eval "(add-to-list 'package-directory-list \"/usr/share/emacs/site-lisp/elpa\")" --eval "(add-to-list 'package-directory-list \"/usr/share/emacs/site-lisp/elpa-src\")" -f package-initialize -L . -l rainbow-delimiters-test.el --eval \(ert-run-tests-batch-and-exit\) returned exit code 1
> make: *** [debian/rules:4: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/09/25/rainbow-delimiters_2.1.5-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lucas@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230925&fusertaguser=lucas@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.


Reply to: