From: Glenn Morris <rgm@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Paul Eggert <eggert@cs.ucla.edu>, 30807@debbugs.gnu.org
Subject: bug#30807: Tramp tests take waaayyy too long and refuse to exit
Date: Wed, 01 Aug 2018 16:31:41 -0400 [thread overview]
Message-ID: <9lmuu5q15e.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87bmfm4ujj.fsf@gmx.de> (Michael Albinus's message of "Sat, 17 Mar 2018 15:59:44 +0100")
With current master, tramp-archive-tests are very slow.
My time to run "make -j8 check" is 3 minutes.
If I remove tramp-archive-tests.el, it changes to 30 seconds.
Here are the slowest tests. Perhaps anything that takes more than 10
seconds should be tagged expensive?
LONG-RUNNING TESTS
------------------
passed 10/22 tramp-archive-test11-copy-file (30.784306 sec)
passed 11/22 tramp-archive-test15-copy-directory (20.679223 sec)
passed 12/13 cl-seq-test-bug24264 (15.896021 sec)
passed 1/3 auto-revert-test00-auto-revert-mode (13.111064 sec)
passed 22/22 tramp-archive-test43-delay-load (11.372054 sec)
passed 21/22 tramp-archive-test43-auto-load (11.365802 sec)
passed 14/22 tramp-archive-test18-file-attributes (10.369735 sec)
passed 8/22 tramp-archive-test08-file-local-copy (10.309309 sec)
passed 13/22 tramp-archive-test17-insert-directory (10.301208 sec)
passed 17/22 tramp-archive-test21-file-links (10.298635 sec)
passed 18/22 tramp-archive-test26-file-name-completion (10.280112 sec)
passed 16/22 tramp-archive-test20-file-modes (10.269900 sec)
passed 15/22 tramp-archive-test19-directory-files-and-attributes (10.256971 sec)
passed 12/22 tramp-archive-test16-directory-files (10.250864 sec)
passed 7/22 tramp-archive-test07-file-exists-p (10.171281 sec)
passed 9/22 tramp-archive-test09-insert-file-contents (10.160516 sec)
passed 3/3 auto-revert-test04-auto-revert-mode-dired (6.042494 sec)
passed 5/8 file-notify-test04-autorevert (6.017824 sec)
passed 1/2 inotify-file-watch-simple (5.002061 sec)
next prev parent reply other threads:[~2018-08-01 20:31 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 [this message]
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=9lmuu5q15e.fsf@fencepost.gnu.org \
--to=rgm@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 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).