Re: Tramp test suite and network access

[Michael Albinus <michael.albinus@gmx.de>]

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.

Furthermore, there is `tramp--test-enabled'. It is intended to check,
whether the Tramp test suite shall run, or whether the tests shall be
skipped. If it doesn't work for you reliably, we shall improve the
checks.

> It'd also be nice to give Emacs /dev/null as its stdin when it's running
> the test suite. Is there any reason we want tests to be able to interact
> with the user?

Yes. IFF you want to run Tramp's tests, you might want to give them a
proper password.

Best regards, Michael.