all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: mattias.engdegard@gmail.com, sbaugh@catern.com
Cc: 73205-done@debbugs.gnu.org, njackson@posteo.net
Subject: bug#73205: 30.0.91; Failed test: uniquify-project-transform at lisp/uniquify-tests.el:130
Date: Sat, 21 Sep 2024 12:47:05 +0300	[thread overview]
Message-ID: <86h6a949uu.fsf@gnu.org> (raw)
In-Reply-To: <86o74rkewo.fsf@gnu.org> (message from Eli Zaretskii on Fri, 13 Sep 2024 13:48:39 +0300)

> Cc: sbaugh@catern.com, 73205@debbugs.gnu.org, njackson@posteo.net
> Date: Fri, 13 Sep 2024 13:48:39 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> 
> > From: "Mattias Engdegård" <mattias.engdegard@gmail.com>
> > Date: Fri, 13 Sep 2024 12:20:14 +0200
> > Cc: "N. Jackson" <njackson@posteo.net>,
> >  Spencer Baugh <sbaugh@catern.com>,
> >  73205@debbugs.gnu.org
> > 
> > 13 sep. 2024 kl. 08.25 skrev Eli Zaretskii <eliz@gnu.org>:
> > 
> > >>     FAILED  uniquify-project-transform
> > 
> > Looks like it fails because there is no current project in a tree that isn't under version control.
> > I added a gate. Spencer, feel free to change if you want something fancier, but I don't think we really need full coverage for non-Git trees.
> 
> >From my POV, skipping this test if not in a Git checkout is fine.
> 
> Thanks.

I see that Mattias modified this test to be skipped outside a Git
checkout, so I'm now closing this bug.





      reply	other threads:[~2024-09-21  9:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12 17:42 bug#73205: 30.0.91; Failed test: uniquify-project-transform at lisp/uniquify-tests.el:130 N. Jackson
2024-09-13  6:25 ` Eli Zaretskii
2024-09-13 10:20   ` Mattias Engdegård
2024-09-13 10:48     ` Eli Zaretskii
2024-09-21  9:47       ` Eli Zaretskii [this message]

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=86h6a949uu.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=73205-done@debbugs.gnu.org \
    --cc=mattias.engdegard@gmail.com \
    --cc=njackson@posteo.net \
    --cc=sbaugh@catern.com \
    /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.