From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 9/9] autobuild-run: extend TODO list
Date: Tue, 25 Nov 2014 22:20:25 +0100 [thread overview]
Message-ID: <20141125222025.1ce56775@free-electrons.com> (raw)
In-Reply-To: <CAAXf6LVgM33BfF2M4xCJebq4s+Rj8XjXzWxwU4YnJ4zotEJZ5w@mail.gmail.com>
Dear Thomas De Schampheleire,
On Tue, 25 Nov 2014 22:09:13 +0100, Thomas De Schampheleire wrote:
> > diff --git a/scripts/autobuild-run b/scripts/autobuild-run
> > index 7fe0b00..a73ccc9 100755
> > --- a/scripts/autobuild-run
> > +++ b/scripts/autobuild-run
> > @@ -47,6 +47,17 @@
> > # - Instead of excluding all configurations that have
> > # BR2_PACKAGE_CLASSPATH=y, improve the script to detect whether the
> > # necessary host machine requirements are there to build classpath.
> > +# - Integrate method check-requirements with the SysInfo class, distinghuishing
> > +# between required and optional dependencies.
> > +# - Extend required dependencies to subversion, mercurial, cpio, wget, python,
> > +# etc.
> > +# - Detect selection of multiple virtual package providers and don't consider it
> > +# a failure
> > +# - Properly handle kill of main script: stop all running children and do not
> > +# print out stacktraces
>
> Brief update on this topic: the autobuild-run code currently kills the
> process group associated with the python process, but it turns out
> that the build jobs are not part of the same process group as the
> python process.
> As far as I can see, the subprocess class should spawn processes into
> the same process group, so maybe make is explicitly changing this?
> Further investigation is needed here, but I think that if we can make
> sure that these processes are part of the same group as the python
> parent process, then the kill of autobuild-run will automatically kill
> the children, as expected.
>
> To visualize the process groups: ps -e -o pid,user,pgid,args --sort pgid
Thanks for this investigation. It would indeed be really nice to be
able to kill just autobuild-run, and be sure that it stops all
underlying builds. We could also catch the signal in autobuild-run, and
kill the build jobs, if we are able to record the necessary information
about them.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-11-25 21:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 19:58 [Buildroot] [PATCH v4 0/9] autobuild-run improvements Thomas De Schampheleire
2014-11-12 19:58 ` [Buildroot] [PATCH v4 1/9] scripts: add python module docopt Thomas De Schampheleire
2014-11-12 19:58 ` [Buildroot] [PATCH v4 2/9] autobuild-run: use docopt for argument parsing Thomas De Schampheleire
2014-11-12 19:58 ` [Buildroot] [PATCH v4 3/9] autobuild-run: add option --make-opts for custom Buildroot options Thomas De Schampheleire
2014-11-12 19:58 ` [Buildroot] [PATCH v4 4/9] autobuild-run: use **kwargs to avoid explicit parameter passthroughs Thomas De Schampheleire
2014-11-12 19:58 ` [Buildroot] [PATCH v4 5/9] autobuild-run: check-requirements does not need to know the login details Thomas De Schampheleire
2014-11-12 19:58 ` [Buildroot] [PATCH v4 6/9] autobuild-run: set LC_ALL=C to not use locale settings of host machine Thomas De Schampheleire
2014-11-12 19:58 ` [Buildroot] [PATCH v4 7/9] autobuild-run: improve the logic to generate build-end.log Thomas De Schampheleire
2014-11-12 19:58 ` [Buildroot] [PATCH v4 8/9] autobuild-run: save config.log files for failed package Thomas De Schampheleire
2014-11-12 19:58 ` [Buildroot] [PATCH v4 9/9] autobuild-run: extend TODO list Thomas De Schampheleire
2014-11-25 21:09 ` Thomas De Schampheleire
2014-11-25 21:20 ` Thomas Petazzoni [this message]
2014-12-04 20:41 ` Thomas De Schampheleire
2014-12-05 8:15 ` Thomas Petazzoni
2014-12-05 12:42 ` Thomas De Schampheleire
2014-11-25 20:36 ` [Buildroot] [PATCH v4 0/9] autobuild-run improvements Thomas De Schampheleire
2014-11-25 20:42 ` Thomas Petazzoni
2014-11-25 21:10 ` Thomas De Schampheleire
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=20141125222025.1ce56775@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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