From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: eggert@cs.ucla.edu, 30807@debbugs.gnu.org
Subject: bug#30807: Tramp tests take waaayyy too long and refuse to exit
Date: Sat, 17 Mar 2018 11:18:58 +0200 [thread overview]
Message-ID: <83k1uboy9p.fsf@gnu.org> (raw)
In-Reply-To: <87efkkrn0z.fsf@gmx.de> (message from Michael Albinus on Fri, 16 Mar 2018 17:41:16 +0100)
> From: Michael Albinus <michael.albinus@gmx.de>
> Date: Fri, 16 Mar 2018 17:41:16 +0100
> Cc: 30807@debbugs.gnu.org
>
> > Also, why not make the TEST_PRINT_TEST_DURATION=1 the default? It's a
> > minor hassle to remember to type "make TEST_PRINT_TEST_DURATION=1".
>
> I have no opinion on this. Glenn? Eli?
If tests becoming slow is something that happens a lot, and we want to
keep track of that, then indeed it sounds like a good idea.
Otherwise, it's just useless clutter.
Alternatively, maybe we should do this only for certain parts of the
suite, where this issue pops frequently.
next prev parent reply other threads:[~2018-03-17 9:18 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83k1uboy9p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=30807@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=michael.albinus@gmx.de \
/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.