public inbox for gentoo-python@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: Mike Gilbert <floppym@gentoo.org>
Cc: gentoo-python@lists.gentoo.org, python@gentoo.org
Subject: Re: [gentoo-python] Re: [distutils-r1] Improvements to parallel builds
Date: Thu, 6 Dec 2012 18:40:46 +0100	[thread overview]
Message-ID: <20121206184046.76639962@pomiocik.lan> (raw)
In-Reply-To: <CAJ0EP400pqqNrTb1tHAkiLRH5B9jhRZxBO739DjD_2_Mumvhtg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]

On Thu, 6 Dec 2012 12:28:37 -0500
Mike Gilbert <floppym@gentoo.org> wrote:

> On Thu, Dec 6, 2012 at 5:54 AM, Michał Górny <mgorny@gentoo.org> wrote:
> >
> > 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.
> >
> 
> The split logs could be handy for developers.
> 
> I had not considered the ugly bug reports that the multi-job build
> will generate. If that becomes a major problem, we might need to
> change the default to single-job, or produce some output to point
> users to the split logs.

It would be great if we had a more general solution here. I will ask
Zac if portage could point users to all *.log files in ${T}.

On the other hand, telling user to attach up to 8 logs feels a bit bad.
But I guess they'll just put them in a tarball.

-- 
Best regards,
Michał Górny

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 316 bytes --]

      reply	other threads:[~2012-12-06 17:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-06 10:54 [gentoo-python] [distutils-r1] Improvements to parallel builds Michał Górny
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 [this message]

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=20121206184046.76639962@pomiocik.lan \
    --to=mgorny@gentoo.org \
    --cc=floppym@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