From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Ross Burton <ross.burton@intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] kill-bb: Add it for killing abnormal bitbake processes
Date: Fri, 02 Aug 2019 16:44:34 +0100 [thread overview]
Message-ID: <30a064b664f500e1ad1c81c97c2e93bb78034e3c.camel@linuxfoundation.org> (raw)
In-Reply-To: <67a9995b-8401-7308-bb0b-b6b81da03abb@intel.com>
On Fri, 2019-08-02 at 11:21 +0100, Ross Burton wrote:
> On 02/08/2019 11:24, Robert Yang wrote:
> > There might be processes left after Ctr-C, e.g.:
> > $ rm -f tmp/cache/default-glibc/qemux86/x86_64/
> > $ bitbake -p
> >
> > Press 'Ctrl-C' multiple times during parsing, then bitbake
> > processes may not
> > exit, and the worse is that we can't start bitbake again, we can't
> > always
> > reproduce this, but sometime. We can only use "ps ux" to find the
> > processes and
> > kill them one by one. This tool can kill all of them easily.
> I've noticed this, and also noticed that it got a lot worse recently.
>
> But let's fix bitbake instead of adding tools to work around it?
Heh. As someone who spends a lot of time trying to debug this, I must
admit I could use such a script so I'm torn on this one!
Cheers,
Richard
next prev parent reply other threads:[~2019-08-02 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 10:24 [PATCH 0/1] kill-bb: Add it for killing abnormal bitbake processes Robert Yang
2019-08-02 10:24 ` [PATCH 1/1] " Robert Yang
2019-08-02 10:21 ` Ross Burton
2019-08-02 10:25 ` Mikko.Rapeli
2019-08-02 15:44 ` Richard Purdie [this message]
2019-08-06 10:43 ` Robert Yang
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=30a064b664f500e1ad1c81c97c2e93bb78034e3c.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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 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.