GNU bug report logs - #70721
[BUG] failed on test case python-tests--python-nav-end-of-statement--infloop

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#70721: closed ([BUG] failed on test case python-tests--python-nav-end-of-statement--infloop)
Date: Thu, 02 May 2024 18:57:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Thu, 02 May 2024 21:56:10 +0300
with message-id <86r0ekjb5h.fsf <at> gnu.org>
and subject line Re: bug#70721: [BUG] failed on test case python-tests--python-nav-end-of-statement--infloop
has caused the debbugs.gnu.org bug report #70721,
regarding [BUG] failed on test case python-tests--python-nav-end-of-statement--infloop
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
70721: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=70721
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Lin Sun <sunlin7.mail <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: [BUG] failed on test case
 python-tests--python-nav-end-of-statement--infloop
Date: Thu, 2 May 2024 16:25:41 +0000

Hi,

Running 1 tests (2024-05-02 15:49:20+0000, selector
‘python-tests--python-nav-end-of-statement--infloop’)
Test python-tests--python-nav-end-of-statement--infloop backtrace:
  ert-fail(((should-error (let ((debug-on-error nil)) (python-nav-end-
  (if errorp5298 nil (ert-fail (append (funcall form-description-fn-52
  (let ((errorp5298 nil) (form-description-fn-5299 #'(lambda nil form-
  (let (form-description-5297) (let ((errorp5298 nil) (form-descriptio
  (let ((value-5296 (gensym "ert-form-evaluation-aborted-"))) (let (fo
  (let ((python-indent-guess-indent-offset nil)) (python-mode) (insert
  (progn (let ((python-indent-guess-indent-offset nil)) (python-mode)
  (unwind-protect (progn (let ((python-indent-guess-indent-offset nil)
  (save-current-buffer (set-buffer temp-buffer) (unwind-protect (progn
  (let ((temp-buffer (generate-new-buffer " *temp*" t))) (save-current
  (closure (t) nil (let ((temp-buffer (generate-new-buffer " *temp*" t
  #[0 "\303\300!\11>\204\17\0\304\305\306\300D\"\210\300\307H\303\1!\n
  handler-bind-1(#[0 "\303\300!\11>\204\17\0\304\305\306\300D\"\210\30
  ert--run-test-internal(#s(ert--test-execution-info :test ... :result
  ert-run-test(#s(ert-test :name python-tests--python-nav-end-of-state
  ert-run-or-rerun-test(#s(ert--stats :selector python-tests--python-n
  ert-run-tests(python-tests--python-nav-end-of-statement--infloop #[3
  ert-run-tests-batch(python-tests--python-nav-end-of-statement--inflo
  eval((ert-run-tests-batch 'python-tests--python-nav-end-of-statement
  command-line-1(("-l" "ert" "-l" "python-tests.el" "-eval" "(ert-run-
  command-line()
  normal-top-level()
Test python-tests--python-nav-end-of-statement--infloop condition:
    (ert-test-failed
     ((should-error (let (...) (python-nav-end-of-statement))) :form
      (let ((debug-on-error nil)) (python-nav-end-of-statement)) :value
      #<marker in no buffer> :fail-reason "did not signal an error"))
   FAILED  1/1  python-tests--python-nav-end-of-statement--infloop
(0.000464 sec) at python-tests.el:7367

Ran 1 tests, 0 results as expected, 1 unexpected (2024-05-02
15:49:20+0000, 0.108988 sec)

1 unexpected results:
   FAILED  python-tests--python-nav-end-of-statement--infloop

[Message part 3 (message/rfc822, inline)]

From: Eli Zaretskii <eliz <at> gnu.org>
To: Lin Sun <sunlin7.mail <at> gmail.com>
Cc: 70721-done <at> debbugs.gnu.org
Subject: Re: bug#70721: [BUG] failed on test case
 python-tests--python-nav-end-of-statement--infloop
Date: Thu, 02 May 2024 21:56:10 +0300

> From: Lin Sun <sunlin7.mail <at> gmail.com>
> Date: Thu, 2 May 2024 18:27:45 +0000
> Cc: 70721 <at> debbugs.gnu.org
> 
> On Thu, May 2, 2024 at 6:18 PM Eli Zaretskii <eliz <at> gnu.org> wrote:
> >
> >
> > That test is marked unstable, which means it can fail in some cases
> > and succeed in others.  So the fact that it could fail is already
> > known, and I wonder why you are reporting this here?
> Thank you for the explanation, according to the test case name
> "*-infloop" seems the case failed means there was an infloop that
> happened, that's why I reported it here.
> Please close this ticket for it's an unstable case. Thanks.

Thanks, done.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.