From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 71566@debbugs.gnu.org
Subject: bug#71566: 30.0.50; test-custom-opts shows errors
Date: Sat, 15 Jun 2024 15:24:52 +0300 [thread overview]
Message-ID: <86y176tmuj.fsf@gnu.org> (raw)
In-Reply-To: <87sexeobdt.fsf@gmx.de> (bug-gnu-emacs@gnu.org)
> Date: Sat, 15 Jun 2024 10:31:26 +0200
> From: Michael Albinus via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
>
> --8<---------------cut here---------------start------------->8---
> # make -C test test-custom-opts
> ...
> Test check-for-wrong-custom-opts condition:
> (ert-test-failed
> ((should (null (cus-test-opts t))) :form
> (null
> ((php-ts-mode-ws-workers :type-error nil ...)
> (org-src-lang-modes :type-error ... ...)
> (php-ts-mode-php-config :type-error nil ...)
> (php-ts-mode-ws-document-root :type-error nil ...)
> (php-ts-mode-ws-port :type-error nil ...)))
> :value nil))
> FAILED 1/1 check-for-wrong-custom-opts (134.958959 sec) at misc/test-custom-opts.el:33
> --8<---------------cut here---------------end--------------->8---
How does one get a human-readable description of the problems with
each of the above defcustoms? Without a way of getting such a
description, this test is utterly useless, and should never be run!
next prev parent reply other threads:[~2024-06-15 12:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-15 8:31 bug#71566: 30.0.50; test-custom-opts shows errors Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-15 12:24 ` Eli Zaretskii [this message]
2024-06-15 12:59 ` Mattias Engdegård
2024-06-15 13:21 ` Eli Zaretskii
2024-06-15 14:01 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-15 14:18 ` Ihor Radchenko
2024-06-15 14:24 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-15 14:36 ` Ihor Radchenko
2024-06-15 14:40 ` Mattias Engdegård
2024-06-15 14:48 ` Ihor Radchenko
2024-06-15 14:49 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-16 8:03 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86y176tmuj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71566@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).