Subject: Re: bug#42538: 28.0.50; tramp-test35-remote-path test timing out on macOS

From: Philipp Stephani <[email-masked]>
Date: Sat, 1 Aug 2020 21:24:28 +0200

Am Sa., 1. Aug. 2020 um 20:15 Uhr schrieb Michael Albinus
<[email-masked]>:
>
> Philipp Stephani <[email-masked]> writes:
>
> Hi Philipp,
>
> > Even that assumption doesn't hold, even if restricted to a single
> > operating system. See e.g. the per-architecture signal number table at
> > https://man7.org/linux/man-pages/man7/signal.7.html.
> > How about using the fallback ("Signal #123") in all cases? In practice
> > the signal descriptions aren't portable, so users can't parse them
> > anyway.
>
> I've tried an alternative implementation, getting the string from the
> remote host (and caching it then). Pushed to master. Could you, pls, check?

It doesn't hang for me any more, thanks. Now I only get the "normal"
test failure:

Test tramp-test33-environment-variables condition:
    (ert-test-failed
     ((should
       (string-equal
(format "%s,tramp:%s" emacs-version tramp-version)
(funcall this-shell-command-to-string "echo -n ${INSIDE_EMACS:-bla}")))
      :form
      (string-equal "28.0.50,tramp:2.5.0-pre" "-n 28.0.50,tramp:2.5.0-pre
")
      :value nil))
   FAILED  45/68  tramp-test33-environment-variables (0.198462 sec)

It looks like this "echo" command/builtin doesn't support "-n".