public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH v2] SyncManager.async: initialize attributes before fork (bug 561234)
Date: Wed, 23 Sep 2015 16:06:57 -0700	[thread overview]
Message-ID: <20150923160657.454e6ecc.dolsen@gentoo.org> (raw)
In-Reply-To: <56032C4A.8070704@gentoo.org>

On Wed, 23 Sep 2015 15:48:42 -0700
Zac Medico <zmedico@gentoo.org> wrote:

> On 09/23/2015 02:58 PM, Brian Dolbec wrote:
> > OK, looks good
> 
> Thanks.
> 
> > 
> > I suppose we'll need to do another release soon, but how long
> > should we wait...(new repoman code) or should we just patch 2.2.21
> 
> Well, you ran repoman on the whole tree and compared the output to the
> old version, right? Did you find any problems there? If not, and long
> as you've tested it with a few commits, I'd say that's enough to
> testing to release it.
> 
> So, I think we're ready to cut a new release as soon as we have the
> "portage-2.2.21 ignores PORTAGE_RSYNC_EXTRA_OPTS" bug fixed:
> 
> https://bugs.gentoo.org/show_bug.cgi?id=561240

well, I had the terminal set for 40,000 lines of scrollback but that
wasn't enough.  I know, I should have redirected the output to a file
It also took about 4 hours...  It did complete with out any tracebacks.

I'll set it up to do simultaneous runs tonight. It certainly didn't tax
this system for cpu power or memory... I suppose it'll put the zfs
caching to the test too :)   And compare the results tomorrow.
-- 
Brian Dolbec <dolsen>



      reply	other threads:[~2015-09-23 23:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-23 16:18 [gentoo-portage-dev] [PATCH] SyncManager.async: initialize attributes before fork (bug 561234) Zac Medico
2015-09-23 19:14 ` [gentoo-portage-dev] [PATCH v2] " Zac Medico
2015-09-23 21:58   ` Brian Dolbec
2015-09-23 22:48     ` Zac Medico
2015-09-23 23:06       ` Brian Dolbec [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=20150923160657.454e6ecc.dolsen@gentoo.org \
    --to=dolsen@gentoo.org \
    --cc=gentoo-portage-dev@lists.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