[Buildroot] [PATCH v4 9/9] autobuild-run: extend TODO list

Thomas De Schampheleire thomas.de.schampheleire at gmail.com
Thu Dec 4 20:41:24 UTC 2014

On Tue, Nov 25, 2014 at 10:20 PM, Thomas Petazzoni
<thomas.petazzoni at free-electrons.com> wrote:
> 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.

Brief update: the piece of the puzzle that is causing a new process
group to be spawned is the 'timeout' command. Everything started under
the timeout command runs in its own process group, different than the
one of the python process. Therefore, killing the python process group
does not kill the timeout+make command.

The solution is to use subprocess.Popen instead of subprocess.call so
we can obtain the pid of the timeout call, and change the signal
handler to explicitly kill this second process group too.

I still have to make the changes in autobuild-run (currently worked on
a simple test program), and will submit patches when ready...

Best regards,

More information about the buildroot mailing list