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

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,
> when I start emacs-30 -Q, then `M-x load-file
> ~/src/emacs/emacs-30/test/lisp/dabbrev-tests.el', then kill all
> non-hidden buffers except *scratch*, and then run `M-x ert', all tests
> pass.  Since the batch run is also used by `make check', I've assumed
> that, since the tests succeed (at least for me) in this mode, they are
> valid regression tests.
>
> In contrast, when I start emacs -Q, visit
> ~/src/emacs/emacs-30/test/lisp/dabbrev-tests.el, evaluate the buffer and
> run `M-x ert', then I get five test failures:
> dabbrev-expand-test-other-buffer-{1,2,3,4} and
> dabbrev-expand-after-killing-buffer.  The latter fails because
> dabbrev-expand finds an expansion in the test file buffer (but succeeds
> when there is no such buffer, as in the previous run starting with -Q).
> The four other tests fail possibly for the same reason; however, these
> four tests fail in this way since being introduced in commit 8113b5c562
> (see
> https://lists.gnu.org/archive/html/bug-gnu-emacs/2024-10/msg01752.html),
> so it puzzles me that you only see just two of those failures and only
> after my latest commit.  (However, I did get the same three failures you
> reported when I ran ert on the test file from commit bd8a6f70fb,
> i.e. the one prior to the above commit, but only after uncommenting the
> code lines that are commented out in that commit.  Could it be that you
> accidentally tested using that previous commit with those code lines
> uncommented?)
>
> Steve Berman

Hi Steve,

my testbench is running "make check -j24" on a fresh checkout on
x86_64-pc-linux-gnu for few different configurations.  For instance I
can see the failures on the latest emacs-30
e618d5ae941d005e9da6d5d5cba68cc0ecade0e5 configured with
"--with-native-compilation=no --with-x-toolkit=no".

Test dabbrev-expand-test-other-buffer-3 backtrace:
  signal(ert-test-failed (((should (string= (buffer-string) "Indic and
  ert-fail(((should (string= (buffer-string) "Indic and")) :form (stri
  #f(compiled-function () #<bytecode 0x15984b7a4b7dc916>)()
  #f(compiled-function () #<bytecode 0x1ea04fa01345ba2a>)()
  handler-bind-1(#f(compiled-function () #<bytecode 0x1ea04fa01345ba2a
  ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
  ert-run-test(#s(ert-test :name dabbrev-expand-test-other-buffer-3 :d
  ert-run-or-rerun-test(#s(ert--stats :selector ... :tests ... :test-m
  ert-run-tests((not (or (tag :expensive-test) (tag :unstable))) #f(co
  ert-run-tests-batch((not (or (tag :expensive-test) (tag :unstable)))
  ert-run-tests-batch-and-exit((not (or (tag :expensive-test) (tag :un
  eval((ert-run-tests-batch-and-exit '(not (or (tag :expensive-test) (
  command-line-1(("-L" ":." "-l" "ert" "--eval" "(setq treesit-extra-l
  command-line()
  normal-top-level()
Test dabbrev-expand-test-other-buffer-3 condition:
    (ert-test-failed
     ((should (string= (buffer-string) "Indic and")) :form
      (string= "Indic\")) (execute-kbd-macro" "Indic and") :value nil
      :explanation
      (arrays-of-different-length 27 9 "Indic\")) (execute-kbd-macro"
                                  "Indic and" first-mismatch-at 5)))
   FAILED  11/16  dabbrev-expand-test-other-buffer-3 (0.042668 sec) at lisp/dabbrev-tests.el:175


Test dabbrev-expand-test-other-buffer-4 backtrace:
  user-error("No%s dynamic expansion for `%s' found" "" "execute-kbd-m
  dabbrev-expand(nil)
  funcall-interactively(dabbrev-expand nil)
  command-execute(dabbrev-expand)
  execute-kbd-macro([73 110 100 134217775])
  #f(compiled-function () #<bytecode -0x15ea54be0ab851ac>)()
  #f(compiled-function () #<bytecode 0x1ea04fa01345ba2a>)()
  handler-bind-1(#f(compiled-function () #<bytecode 0x1ea04fa01345ba2a
  ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
  ert-run-test(#s(ert-test :name dabbrev-expand-test-other-buffer-4 :d
  ert-run-or-rerun-test(#s(ert--stats :selector ... :tests ... :test-m
  ert-run-tests((not (or (tag :expensive-test) (tag :unstable))) #f(co
  ert-run-tests-batch((not (or (tag :expensive-test) (tag :unstable)))
  ert-run-tests-batch-and-exit((not (or (tag :expensive-test) (tag :un
  eval((ert-run-tests-batch-and-exit '(not (or (tag :expensive-test) (
  command-line-1(("-L" ":." "-l" "ert" "--eval" "(setq treesit-extra-l
  command-line()
  normal-top-level()
Test dabbrev-expand-test-other-buffer-4 condition:
    (user-error "No dynamic expansion for `execute-kbd-macroInd' found")
   FAILED  12/16  dabbrev-expand-test-other-buffer-4 (0.021285 sec) at lisp/dabbrev-tests.el:194


Test dabbrev-expand-after-killing-buffer backtrace:
  signal(ert-test-failed (((should (string= msg "No further dynamic ex
  ert-fail(((should (string= msg "No further dynamic expansion for ‘ab
  #f(compiled-function () #<bytecode 0x18257815d6a0b741>)()
  #f(compiled-function () #<bytecode 0x1ea04fa01345ba2a>)()
  handler-bind-1(#f(compiled-function () #<bytecode 0x1ea04fa01345ba2a
  ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
  ert-run-test(#s(ert-test :name dabbrev-expand-after-killing-buffer :
  ert-run-or-rerun-test(#s(ert--stats :selector ... :tests ... :test-m
  ert-run-tests((not (or (tag :expensive-test) (tag :unstable))) #f(co
  ert-run-tests-batch((not (or (tag :expensive-test) (tag :unstable)))
  ert-run-tests-batch-and-exit((not (or (tag :expensive-test) (tag :un
  eval((ert-run-tests-batch-and-exit '(not (or (tag :expensive-test) (
  command-line-1(("-L" ":." "-l" "ert" "--eval" "(setq treesit-extra-l
  command-line()
  normal-top-level()
Test dabbrev-expand-after-killing-buffer condition:
    (ert-test-failed
     ((should (string= msg "No further dynamic expansion for ‘ab’ found"))
      :form
      (string= "No further dynamic expansion for `ab' found"
               "No further dynamic expansion for ‘ab’ found")
      :value nil :explanation
      (array-elt 33
                 (different-atoms (96 "#x60" "?`") (8216 "#x2018" "?‘")))))
   FAILED   3/16  dabbrev-expand-after-killing-buffer (0.001730 sec) at lisp/dabbrev-tests.el:278

Thanks

  Andrea



  reply	other threads:[~2024-12-03  8:14 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 [this message]
2024-12-03  9:40         ` Stephen Berman
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=yp1v7w1fajh.fsf@fencepost.gnu.org \
    --to=acorallo@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=stephen.berman@gmx.net \
    /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).