GNU bug report logs -
#42538
28.0.50; tramp-test35-remote-path test timing out on macOS
Previous Next
Reported by: Philipp <p.stephani2 <at> gmail.com>
Date: Sat, 25 Jul 2020 19:05:02 UTC
Severity: normal
Tags: fixed
Found in version 28.0.50
Fixed in versions 27.2, 28.1
Done: Michael Albinus <michael.albinus <at> gmx.de>
Bug is archived. No further changes may be made.
Full log
Message #58 received at 42538 <at> debbugs.gnu.org (full text, mbox):
Am Sa., 1. Aug. 2020 um 20:15 Uhr schrieb Michael Albinus
<michael.albinus <at> gmx.de>:
>
> Philipp Stephani <p.stephani2 <at> gmail.com> 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".
This bug report was last modified 4 years and 296 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.