From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Odd hang in python waiting for child; strace wakes hung process?
Date: Wed, 21 Mar 2018 19:20:00 -0000 [thread overview]
Message-ID: <877eq5fedf.fsf@Rainer.invalid> (raw)
In-Reply-To: <CAPF-yOYzTr-jh__S_imaAcdk5Vf4tGD1xFLuTDu4-qsg_+HiCA@mail.gmail.com> (Dan Kegel's message of "Wed, 21 Mar 2018 10:36:48 -0700")
Dan Kegel writes:
> I've been happily using cygwin to run buildbot slaves for several
> years. However, periodically they hang at the end of executing git.
> It kind of smells like SIGCHLD isn't delivered somehow.
That smells like it's the same as a longstanding problem I have with
certain Perl tests and a few (a bit too complicated) Perl scripts at
work. I have never been able to reproduce it in a way that might enable
Corinna to have a look, unfortunately.
> My next sensible step is to use an up to date version of buildbot's slave
> (I'm running a very old one at the moment), but it seems kind of
> fishy that strace could wake the process up.
Well, with the sporadic hanging/defunct processes at work my routine is
to send CONT to all Cygwin processes, then HUP/KILL to anything that's
still not live or gone and then another round of CONT. This works
_most_ of the time, anything more stubborn I /bin/kill -f usually.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-03-21 18:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 17:55 Dan Kegel
2018-03-21 19:20 ` Achim Gratz [this message]
2018-03-21 22:09 ` Dan Kegel
2018-03-22 7:38 ` Brian Inglis
2018-03-22 17:10 ` Corinna Vinschen
2018-03-22 21:05 ` Dan Kegel
2018-03-24 1:54 ` Brian Inglis
2018-03-25 18:12 ` Corinna Vinschen
2018-03-25 22:16 ` Brian Inglis
2018-03-22 17:33 ` Achim Gratz
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=877eq5fedf.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.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.
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).