From: Michael Albinus <michael.albinus@gmx.de>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 30807@debbugs.gnu.org
Subject: bug#30807: Tramp tests take waaayyy too long and refuse to exit
Date: Wed, 14 Mar 2018 16:36:01 +0100 [thread overview]
Message-ID: <87d106u0ta.fsf@gmx.de> (raw)
In-Reply-To: <87efkn9g9u.fsf@gmx.de> (Michael Albinus's message of "Wed, 14 Mar 2018 10:07:41 +0100")
Michael Albinus <michael.albinus@gmx.de> writes:
Hi Paul,
>> Because of these problems I no longer routinely run "make check".
>
> This is bad, and we shall fix it.
As a first step, I have extended ert to print the duration time of single
tests in batch mode. This is disabled by default, you can enable it via
make TEST_PRINT_TEST_DURATION=1 ...
Pushed to master.
If you run ert interactively, there is already the almost unknown key
"T" in the *ert* buffer, which gives a nice, sorted overview of the
duration times.
Best regards, Michael.
next prev parent reply other threads:[~2018-03-14 15:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 20:48 bug#30807: Tramp tests take waaayyy too long and refuse to exit Paul Eggert
2018-03-13 21:27 ` Glenn Morris
2018-03-14 15:54 ` Michael Albinus
2018-03-14 21:33 ` Glenn Morris
2018-03-16 15:22 ` Michael Albinus
2018-03-14 9:07 ` Michael Albinus
2018-03-14 15:36 ` Michael Albinus [this message]
2018-03-15 0:17 ` Paul Eggert
2018-03-15 10:36 ` Michael Albinus
2018-03-16 16:03 ` Paul Eggert
2018-03-16 16:41 ` Michael Albinus
2018-03-16 18:58 ` Glenn Morris
2018-03-16 21:35 ` Paul Eggert
2018-03-17 14:59 ` Michael Albinus
2018-03-17 15:23 ` Noam Postavsky
2018-03-19 0:02 ` Paul Eggert
2018-08-01 20:31 ` Glenn Morris
2018-08-01 20:54 ` Michael Albinus
2018-08-08 13:40 ` Michael Albinus
2018-08-10 22:56 ` Glenn Morris
2018-03-17 9:18 ` Eli Zaretskii
2018-03-17 9:30 ` Michael Albinus
2018-03-14 21:01 ` Glenn Morris
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=87d106u0ta.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=30807@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/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).