Re: Tramp test suite and network access

[Daniel Colascione <dancol@dancol.org>]

[-- Attachment #1: Type: text/plain, Size: 905 bytes --]

On 04/21/2014 01:09 AM, Michael Albinus wrote:
> Daniel Colascione <dancol@dancol.org> writes:
> 
> Hi Daniel,
> 
>> Can we change the tramp test suite so that, by default, it doesn't try
>> to access the network? If a host isn't connected to the network, tests
>> can hang for a long time with no user-visible explanation, and even if
>> network connectivity is available, ssh to the local system isn't
>> guaranteed to work, or work without asking for input. (The tramp tests
>> constantly ask me whether I want to connect.)
> 
> You can always set $REMOTE_TEMPORARY_FILE_DIRECTORY to /dev/null, prior
> to running the test suite. See the Commentary section of tramp-tests.el.

Or we can set it to /dev/null and let users who want to run network
tests override it. And you can always mock the network side of the tramp
tests, which today are pretty slow even when they run properly.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]