all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: Glenn Morris <rgm@gnu.org>, Lars Ingebrigtsen <larsi@gnus.org>,
	43004@debbugs.gnu.org
Subject: bug#43004: 28.0.50; Test failures due to symlinked Emacs sources
Date: Sat, 31 Oct 2020 03:39:12 +0200	[thread overview]
Message-ID: <3a490fed-c53e-eabe-34a6-427833a71c45@yandex.ru> (raw)
In-Reply-To: <87a6w3mmma.fsf@rub.de>

On 30.10.2020 23:26, Stephen Berman wrote:
> That's what I did in my patch in<87r1pyz27k.fsf@gmx.net>
> (https://debbugs.gnu.org/cgi/bugreport.cgi?msg=11;att=1;bug=43004) and
> initially concluded that with that patch "I now get no unexpected
> failures when running the tests in batch mode, though when run
> interactively xref-elisp-test-find-defs-defgeneric-implicit-generic
> still fails."

But looking at that patch, you moved some of the 'file-truename' calls, 
at least, down inside the test definitions, to produce the "expected" 
values.

What happens if you just remove that 'file-truename' call without adding 
it somewhere else?





  reply	other threads:[~2020-10-31  1:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-23 21:27 bug#43004: 28.0.50; Test failures due to symlinked Emacs sources Stephen Berman
2020-10-16  8:34 ` Lars Ingebrigtsen
2020-10-16 14:15   ` Stephen Berman
2020-10-16 14:37     ` Lars Ingebrigtsen
2020-10-16 14:48       ` Stephen Berman
2020-10-16 20:20         ` Dmitry Gutov
2020-10-16 20:54           ` Stephen Berman
2020-10-29 23:02             ` Dmitry Gutov
2020-10-30 21:26               ` Stephen Berman
2020-10-31  1:39                 ` Dmitry Gutov [this message]
2020-10-31 21:30                   ` Stephen Berman
2020-10-17  6:39           ` Lars Ingebrigtsen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3a490fed-c53e-eabe-34a6-427833a71c45@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=43004@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=rgm@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.