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>,
	Lars Ingebrigtsen <larsi@gnus.org>
Cc: 43004@debbugs.gnu.org
Subject: bug#43004: 28.0.50; Test failures due to symlinked Emacs sources
Date: Fri, 16 Oct 2020 23:20:19 +0300	[thread overview]
Message-ID: <7002ef78-2d34-a812-5d38-5b4423d3068e@yandex.ru> (raw)
In-Reply-To: <87mu0mz0op.fsf@gmx.net>

On 16.10.2020 17:48, Stephen Berman wrote:
> Yes, please.  I also just realized that I had run the patched batch mode
> tests from my home directory, i.e., following the symlink.  When I run
> them from the source directory without following the symlink, I get the
> same five failures again (i.e., with the patch) that I had gotten before
> without the patch.  So much for that attempt.

So... the patch doesn't work?

I'm not sure what would be the best change here, or whether your usage 
is something we absolutely need to support in 'make check' (Lars? do 
we?), but one thing that should help is the exact examples of strings ( 
absolute file names) that mismatch.





  reply	other threads:[~2020-10-16 20:20 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 [this message]
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
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=7002ef78-2d34-a812-5d38-5b4423d3068e@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=43004@debbugs.gnu.org \
    --cc=larsi@gnus.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.