unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: Andrea Corallo <acorallo@gnu.org>
Cc: Michael Albinus <michael.albinus@gmx.de>, emacs-devel@gnu.org
Subject: Re: emacs-30 6bca138d60e: Fix latest test for dabbrev-expand
Date: Tue, 03 Dec 2024 10:40:30 +0100	[thread overview]
Message-ID: <87wmghcdf5.fsf@gmx.net> (raw)
In-Reply-To: <yp1v7w1fajh.fsf@fencepost.gnu.org> (Andrea Corallo's message of "Tue, 03 Dec 2024 03:14:26 -0500")

On Tue, 03 Dec 2024 03:14:26 -0500 Andrea Corallo <acorallo@gnu.org> wrote:

> Stephen Berman <stephen.berman@gmx.net> writes:
>
>> On Mon, 02 Dec 2024 15:45:23 -0500 Andrea Corallo <acorallo@gnu.org> wrote:
>>
>>> Stephen Berman via Mailing list for Emacs changes <emacs-diffs@gnu.org>
>>> writes:
>>>
>>>> branch: emacs-30
>>>> commit 6bca138d60e47d0fbab4faf8e83c5b9b319f260d
>>>> Author: Stephen Berman <stephen.berman@gmx.net>
>>>> Commit: Stephen Berman <stephen.berman@gmx.net>
>>>>
>>>>     Fix latest test for dabbrev-expand
>>>>
>>>>     * test/lisp/dabbrev-tests.el (dabbrev-expand-after-killing-buffer):
>>>>     Fix typo in a 'should' test, use part of return value of 'should-error'
>>>>     test, and remove mistaken and unfounded FIXME comment.
>>>
>>> Hello Stephen,
>>>
>>> this commit is introducing in my test-bed the following three failures
>>> in emacs-30: dabbrev-expand-test-other-buffer-4,
>>> dabbrev-expand-test-other-buffer-3, dabbrev-expand-after-killing-buffer.
>>> Could you please have a look?
>>>
>>>   Andrea
>>
>> How does your testbed run the tests?  When I invoke `emacs-30 -batch -l
>> ~/src/emacs/emacs-30/test/lisp/dabbrev-tests.el -f
>> ert-run-tests-batch-and-exit' from the shell, all tests pass.  Likewise,
[...]
> my testbench is running "make check -j24" on a fresh checkout on
[...]

On Tue, 03 Dec 2024 09:19:46 +0100 Michael Albinus <michael.albinus@gmx.de> wrote:

[...]
> dabbrev-tests.el is broken in the emacs-30 branch. Running 'make -C test
> dabbrev-tests.log' yields the appended log file.

It seems that substitute-command-keys applies to user-error messages in
ert batch runs but not when executing `make check'.  I missed the latter
because when I committed that patch, the emacs-30 build was broken due
to the librsvg version issue, so I couldn't run `make check'.  But since
`make check' had succeeded with my previous commit, I wrongly assumed it
would also succeed this change; I should have waited.  I've now pushed a
workaround (commit 7b8d12e95de to emacs-30) with which both batch runs
and `make check' succeed for me.  Hopefully they do for everyone else
too!

Steve Berman



  reply	other threads:[~2024-12-03  9:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <173314163483.652988.2881826266893472321@vcs3.savannah.gnu.org>
     [not found] ` <20241202121355.3BF7D526A27@vcs3.savannah.gnu.org>
2024-12-02 20:45   ` emacs-30 6bca138d60e: Fix latest test for dabbrev-expand Andrea Corallo
2024-12-02 22:16     ` Stephen Berman
2024-12-03  8:14       ` Andrea Corallo
2024-12-03  9:40         ` Stephen Berman [this message]
2024-12-03  9:55           ` Andrea Corallo
2024-12-03  8:19   ` Michael Albinus

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=87wmghcdf5.fsf@gmx.net \
    --to=stephen.berman@gmx.net \
    --cc=acorallo@gnu.org \
    --cc=emacs-devel@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).