unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Emacs developers <emacs-devel@gnu.org>, Dmitry Gutov <dgutov@yandex.ru>
Subject: Re: master 12ca463 1/4: ; * test/lisp/textmodes/css-mode-tests.el: Add TODO.
Date: Tue, 22 Sep 2020 15:54:09 +0200	[thread overview]
Message-ID: <CADwFkmkROuALu2rSGRkr-2A_GLyburDYqUEUZrhO0cKCAVnzVQ@mail.gmail.com> (raw)
In-Reply-To: <87zh5ihr5p.fsf@gnus.org>

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Yeah, more automatic checks are better, but they can sometimes be
> cumbersome to work with manually...  Fixing the latter somehow would be
> nice.

I usually prefer running tests non-interactively.  My main issue is
that I have to manually scroll to find the failing test in the
compilation buffer.  Perhaps we should adapt the ert format to be more
easily parsable by compilation-mode?  ISTR a discussion like that not
long ago.

I would also like the option to see the full backtrace for a test on
"make check" et al.



  reply	other threads:[~2020-09-22 13:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200921144653.9320.23809@vcs0.savannah.gnu.org>
     [not found] ` <20200921144656.3E99C206ED@vcs0.savannah.gnu.org>
2020-09-21 17:54   ` master 12ca463 1/4: ; * test/lisp/textmodes/css-mode-tests.el: Add TODO Dmitry Gutov
2020-09-21 18:23     ` Stefan Kangas
2020-09-22 13:33       ` Lars Ingebrigtsen
2020-09-22 13:54         ` Stefan Kangas [this message]
2020-09-22 15:06           ` Lars Ingebrigtsen
2020-09-22 18:34             ` Dmitry Gutov
2020-09-22 16:22         ` Stefan Monnier
2020-09-23 13:56           ` Stefan Kangas
2020-09-23 14:28             ` Stefan Monnier
2020-09-23 15:44               ` Stefan Kangas
2020-09-22 19:32       ` Dmitry Gutov
2020-09-23 14:06         ` Stefan Kangas

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=CADwFkmkROuALu2rSGRkr-2A_GLyburDYqUEUZrhO0cKCAVnzVQ@mail.gmail.com \
    --to=stefan@marxist.se \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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).