unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Question about test failure on Hydra
Date: Tue, 01 Aug 2017 17:23:36 +0200	[thread overview]
Message-ID: <87efsv71mv.fsf@rosalinde> (raw)
In-Reply-To: <83379b1jqb.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 01 Aug 2017 16:49:16 +0300")

On Tue, 01 Aug 2017 16:49:16 +0300 Eli Zaretskii <eliz@gnu.org> wrote:

>> From: Stephen Berman <stephen.berman@gmx.net>
>> Cc: emacs-devel@gnu.org
>> Date: Tue, 01 Aug 2017 11:57:14 +0200
>> 
>> On Tue, 01 Aug 2017 06:12:49 +0300 Eli Zaretskii <eliz@gnu.org> wrote:
>> 
>> >> From: Stephen Berman <stephen.berman@gmx.net>
>> >> Cc: emacs-devel@gnu.org
>> >> Date: Mon, 31 Jul 2017 11:20:10 +0200
>> >> 
>> >> (dired test-dir) reverts an existing Dired buffer, because of setting
>> >> dired-auto-revert-buffer to t.  (When I step through the code, it is
>> >> after reverting that point moves to the subdirectory line
>> >
>> > By "the point moves" you mean what dired-restore-positions does?
>> 
>> Yes.
>
> Then I'd begin with logging the values saved in POSITIONS that
> dired-restore-positions uses, perhaps the recorded positions are
> sometimes wrong.  Then we could take it from there, either by looking
> how the values are recorded or how they are restored.

In commit c5305ff6 Tino Calancha added more assertions to track point,
so this may already be enough to locate the problem if the test fails in
Hydra again.  If it isn't, we can add still more.

Steve Berman



  reply	other threads:[~2017-08-01 15:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-30 15:50 Question about test failure on Hydra Stephen Berman
2017-07-30 15:59 ` Eli Zaretskii
2017-07-30 20:23   ` Stephen Berman
2017-07-31  3:26     ` Eli Zaretskii
2017-07-31  9:20       ` Stephen Berman
2017-08-01  3:12         ` Eli Zaretskii
2017-08-01  9:57           ` Stephen Berman
2017-08-01 13:49             ` Eli Zaretskii
2017-08-01 15:23               ` Stephen Berman [this message]
2017-08-02 15:27                 ` Stephen Berman
2017-08-01  4:39         ` Tino Calancha
2017-08-01  9:57           ` Stephen Berman
2017-08-01 10:17             ` Tino Calancha
2017-08-01 10:47               ` Stephen Berman
2017-08-05 13:07               ` Tino Calancha
2017-08-05 21:34                 ` Stephen Berman
2017-08-03 19:41 ` tagging ERT tests with bug numbers (was: Question about test failure on Hydra) Ted Zlatanov
2017-08-04  7:22   ` tagging ERT tests with bug numbers Michael Albinus
2017-08-04 13:28     ` Ted Zlatanov
2017-08-04 14:50       ` 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=87efsv71mv.fsf@rosalinde \
    --to=stephen.berman@gmx.net \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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).