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 10:07:41 +0100 [thread overview]
Message-ID: <87efkn9g9u.fsf@gmx.de> (raw)
In-Reply-To: <1fde81b8-b266-86b8-133a-1bde81145346@cs.ucla.edu> (Paul Eggert's message of "Tue, 13 Mar 2018 13:48:57 -0700")
Paul Eggert <eggert@cs.ucla.edu> writes:
Hi Paul,
> For the past few weeks "make check" has been taking a looooong time on
> Emacs master on my Fedora 27 desktop (AMD Phenom II X4 910e).
All following timings are performed on my 8-years old ThinkPad T500 (Intel
Core2 Duo T9550, 4MB RAM).
Yes, something is wrong. In the emacs-26 branch, I see
--8<---------------cut here---------------start------------->8---
$ time make -C test tramp-tests SELECTOR='$(SELECTOR_DEFAULT)'
28.902u 4.947s 0:36.09 93.7% 0+0k 4448+4568io 0pf+0w
--8<---------------cut here---------------end--------------->8---
The same call in master yields
--8<---------------cut here---------------start------------->8---
$ time make -C test tramp-tests SELECTOR='$(SELECTOR_DEFAULT)'
228.608u 7.401s 4:08.63 94.9% 0+0k 8064+8784io 8pf+0w
--8<---------------cut here---------------end--------------->8---
Up to eight time slower. I will check what's up. (Usually, I run only
the expensive Tramp tests, so I haven't seen this yet)
> and some of the tests in the corresponding script look to be very
> slow. Can this be sped up? Let's mark the slow tests to be expensive,
> so that they are run only if one executes "make check-expensive".
This is already the case. I guess you've uncovered an error, which must
be fixed.
> Worse, there's another long wait here:
>
> GEN lisp/net/tramp-archive-tests.log
>
> after this line is output:
>
> passed 20/22 tramp-archive-test40-file-system-info
I don't see an error here. I get
--8<---------------cut here---------------start------------->8---
$ time make -C test tramp-archive-tests SELECTOR='$(SELECTOR_DEFAULT)'
11.131u 0.678s 0:17.43 67.6% 0+0k 0+104io 0pf+0w
--8<---------------cut here---------------end--------------->8---
This is not superfast (17s duration), but maybe acceptable.
> and here the wait is so long that I gave up trying to run the tests
> and typed control-C to exit them. Presumably the semi-inflooping test
> is tramp-archive-test42-auto-load. (Why is it 42 and not 41? Why are
> there two test42s? I don't know.)
No problem here:
--8<---------------cut here---------------start------------->8---
$ time make -C test tramp-archive-tests SELECTOR='\"tramp-archive-test42-auto-load\"'
1.505u 0.256s 0:02.64 66.2% 0+0k 0+0io 0pf+0w
--8<---------------cut here---------------end--------------->8---
The reasoning for the test numbering is explained in the comment of
tramp-archive-tests.el:
;; The `tramp-archive-testnn-*' tests correspond to the respective
;; tests in tramp-tests.el.
> Worse yet, after I control-C out of "make check" and get a shell
> prompt back, a subsidiary Emacs that is running the Tramp test refuses
> to exit and continues to chew up CPU time in the background until I
> use "kill 3304" (or whatever) to kill it. This really needs to get
> fixed.
I will try to produce some instrumentation for tramp-archive-test42-auto-load
in order to catch your problem.
> Because of these problems I no longer routinely run "make check".
This is bad, and we shall fix it.
Best regards, Michael.
next prev parent reply other threads:[~2018-03-14 9:07 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 [this message]
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
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=87efkn9g9u.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).