From: Andreas Schwab <schwab@linux-m68k.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Philipp Stephani <p.stephani2@gmail.com>, 42538@debbugs.gnu.org
Subject: bug#42538: 28.0.50; tramp-test35-remote-path test timing out on macOS
Date: Fri, 31 Jul 2020 20:59:34 +0200 [thread overview]
Message-ID: <878sez1pex.fsf@igel.home> (raw)
In-Reply-To: <87d04bzhm1.fsf@gmx.de> (Michael Albinus's message of "Fri, 31 Jul 2020 20:04:06 +0200")
On Jul 31 2020, Michael Albinus wrote:
> I see. `tramp-get-signal-strings' is problematic anyway, because it runs
> locally, but shall serve the signal strings for the remote host. Maybe,
> we shall assume standardized signal strings up to 15 only.
Even then you have variation among architectures on Linux alone. For
example, SIGBUS can be 10 or 7.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2020-07-31 18:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-25 19:04 bug#42538: 28.0.50; tramp-test35-remote-path test timing out on macOS Philipp
2020-07-26 9:19 ` Michael Albinus
2020-07-26 14:13 ` Philipp Stephani
2020-07-26 15:52 ` Michael Albinus
2020-07-26 21:39 ` Philipp Stephani
2020-07-27 15:28 ` Michael Albinus
2020-07-29 14:26 ` Michael Albinus
2020-07-29 19:34 ` Philipp Stephani
2020-07-30 11:53 ` Michael Albinus
2020-07-31 15:02 ` Philipp Stephani
2020-07-31 15:22 ` Philipp Stephani
2020-07-31 16:55 ` Michael Albinus
2020-07-31 17:30 ` Philipp Stephani
2020-07-31 18:04 ` Michael Albinus
2020-07-31 18:59 ` Andreas Schwab [this message]
2020-07-31 19:53 ` Philipp Stephani
2020-08-01 18:15 ` Michael Albinus
2020-08-01 19:24 ` Philipp Stephani
2020-08-01 19:27 ` Philipp Stephani
2020-08-02 11:37 ` Michael Albinus
2020-08-02 14:29 ` Philipp Stephani
2020-08-02 15:29 ` Michael Albinus
2020-08-02 11:32 ` 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=878sez1pex.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=42538@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=p.stephani2@gmail.com \
/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.