all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Daniel Colascione <dancol@dancol.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Tramp test suite and network access
Date: Mon, 21 Apr 2014 18:25:26 +0200	[thread overview]
Message-ID: <87lhuyps3t.fsf@gmx.de> (raw)
In-Reply-To: <53546D0B.3090406@dancol.org> (Daniel Colascione's message of "Sun, 20 Apr 2014 17:57:47 -0700")

Daniel Colascione <dancol@dancol.org> writes:

> If a host isn't connected to the network, tests
> can hang for a long time with no user-visible explanation,

Default Tramp timeout is 60 seconds. We could shorten it for the tests
if desired.

OTOH, often I use fencepost.gnu.org as remote counterpart for the tests,
which is useful *because* I have a slow connection to that host. It's
useful to see how Tramp behaves on slow lines.

> and even if network connectivity is available, ssh to the local system
> isn't guaranteed to work, or work without asking for input.

Well, that's the default. But Tramp can run without ssh at all.

> (The tramp tests constantly ask me whether I want to connect.)

Tramp shouldn't ask you; it's the task of `tramp--test-enabled' to check
silently, whether the tests must be skipped.

What does it ask you? A password? It shouldn't. A passphrase? This we
might want to suppress. Something else?

Best regards, Michael.



  parent reply	other threads:[~2014-04-21 16:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-21  0:57 Tramp test suite and network access Daniel Colascione
2014-04-21  7:12 ` Eli Zaretskii
2014-04-21  8:09 ` Michael Albinus
2014-04-21  8:10   ` Daniel Colascione
2014-04-21  8:32     ` Michael Albinus
2014-04-21  8:34       ` Daniel Colascione
2014-04-21  8:40         ` Michael Albinus
2014-04-21  8:40     ` Eli Zaretskii
2014-04-21 16:25 ` Michael Albinus [this message]
2014-04-24  8:27 ` Michael Albinus

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=87lhuyps3t.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=dancol@dancol.org \
    --cc=emacs-devel@gnu.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 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.