public inbox for gentoo-python@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-python@lists.gentoo.org
Cc: python@gentoo.org
Subject: [gentoo-python] [distutils-r1] Improvements to parallel builds
Date: Thu,  6 Dec 2012 11:54:53 +0100	[thread overview]
Message-ID: <1354791297-19239-1-git-send-email-mgorny@gentoo.org> (raw)

A two quick improvements to parallel builds using distutils-r1.


1) use post-fork mode to avoid early output

In other words, you no longer see 'running X for Y' before it is
actually being run.


2) create split logs for each implementation

Aside to the usual soup on stdout, the eclass writes separate build logs
for each implementation to ${T}/build-${EPYTHON}.log.

TODO: replace tee with an awesome use of multitail to display logs
of currently running builds on split-screen.



             reply	other threads:[~2012-12-06 10:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-06 10:54 Michał Górny [this message]
2012-12-06 10:54 ` [gentoo-python] [PATCH distutils-r1 1/4] Don't rely on phase function return code Michał Górny
2012-12-06 10:54 ` [gentoo-python] [PATCH distutils-r1 2/4] Use post-fork mode to avoid early output Michał Górny
2012-12-06 10:54 ` [gentoo-python] [PATCH distutils-r1 3/4] multiprocessing: use the expanded call form Michał Górny
2012-12-06 10:54 ` [gentoo-python] [PATCH distutils-r1 4/4] Create split logs when doing parallel builds Michał Górny
2012-12-06 17:28 ` [gentoo-python] Re: [distutils-r1] Improvements to " Mike Gilbert
2012-12-06 17:40   ` Michał Górny

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=1354791297-19239-1-git-send-email-mgorny@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-python@lists.gentoo.org \
    --cc=python@gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox