From: Tomi Ollila <tomi.ollila@iki.fi>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
debian mipsel buildd maintainers <mipsel@buildd.debian.org>,
Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: build failures on mipsel
Date: Wed, 06 Jun 2018 17:47:32 +0300 [thread overview]
Message-ID: <m2zi08km4b.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <871sdk9edk.fsf@fifthhorseman.net>
On Wed, Jun 06 2018, Daniel Kahn Gillmor wrote:
> On Mon 2018-06-04 17:52:46 -0400, Daniel Kahn Gillmor wrote:
>> I've tried to replicate the problem over on eller.debian.org (the mipsel
>> porterbox) but when i build 0.27~rc1 over there in an schroot, i don't
>> even get to T357 because the emacs_fcc_message() function hangs in this
>> loop (is this known to not work in an schroot or under similar
>> situations?):
>
> This problem appears to be related to some bad interaction with
> screen(1) inside a sid chroot on eller. i note that bash also has
> problems with command line editing in that environment as well.
>
> I'm now running inside of tmux instead, and that problem doesn't happen
> any more.
>
> Furthermore, i can't replicate the failure from the buildd when building
> on eller either. So neither bremner nor i were able to replicate the
> problem.
>
> mipsel porters, do you have any suggestions for next-step debugging?
This is the line to start emacs
# start a detached session with an emacs server
# user's TERM (or 'vt100' in case user's TERM is known dumb
# or unknown) is given to dtach which assumes a minimally
# VT100-compatible terminal -- and emacs inherits that
TERM=$SMART_TERM dtach -n "$TEST_TMPDIR/emacs-dtach-socket.$$" \
sh -c "stty rows 24 cols 80; exec '$TMP_DIRECTORY/run_emacs' \
--no-window-system \
$load_emacs_tests \
--eval '(setq server-name \"$server_name\")' \
--eval '(server-start)' \
--eval '(orphan-watchdog $$)'" || return
my first guess: SMART_TERM is 'screen', and terminfo for that is missing
if not, then some TTY problem, which may break dtach, and if not dtach,
then emacs
my usual try is strace(1):
TERM=$SMART_TERM strace -f dtach -n "$TEST_TMPDIR/emacs-dtach-socket.$$" \
sh -c "stty rows 24 cols 80; exec '$TMP_DIRECTORY/run_emacs' \
--no-window-system \
$load_emacs_tests \
--eval '(setq server-name \"$server_name\")' \
--eval '(server-start)' \
--eval '(orphan-watchdog $$)'" &
(have to be run in background as strace -f will not exit until every child
program have exited...)
and then comb through strace output (-o option to strace may be useful...).
>
> --dkg
next prev parent reply other threads:[~2018-06-06 14:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 21:52 build failures on mipsel Daniel Kahn Gillmor
2018-06-05 2:44 ` David Bremner
2018-06-06 14:15 ` Daniel Kahn Gillmor
2018-06-06 14:59 ` David Bremner
2018-06-05 18:12 ` Tomi Ollila
2018-06-06 14:30 ` Daniel Kahn Gillmor
2018-06-06 14:47 ` Tomi Ollila [this message]
2018-06-06 17:05 ` Daniel Kahn Gillmor
2018-06-07 13:58 ` Daniel Kahn Gillmor
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2zi08km4b.fsf@guru.guru-group.fi \
--to=tomi.ollila@iki.fi \
--cc=dkg@fifthhorseman.net \
--cc=mipsel@buildd.debian.org \
--cc=notmuch@notmuchmail.org \
/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 public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).