From: Mark H Weaver <mhw@netris.org>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 1/7] gnu: gobject-introspection: Update to 1.44.0.
Date: Fri, 24 Apr 2015 18:22:33 -0400 [thread overview]
Message-ID: <87fv7pyxna.fsf@netris.org> (raw)
In-Reply-To: <87d22w6w9f.fsf@netris.org> (Mark H. Weaver's message of "Wed, 22 Apr 2015 11:03:08 -0400")
Mark H Weaver <mhw@netris.org> writes:
> Andreas Enge <andreas@enge.fr> writes:
>
>> Well, in an ideal world, these two patch sets would be built separately,
>> so that any failure could be attributed to one or the other. So I would
>> not call two rebuilds "wasted work" in such a context.
>
> Agreed. If our build farm had enough capacity, this would be ideal.
> I should not have said "wasted work".
>
> Unfortunately, our build farm capacity is quite limited, and its master
> machine is currently lacking in RAM and has extraordinarily poor disk
> performance. For these reasons, at present, it requires a great deal of
> hand-holding to keep it from becoming overloaded to the point of being
> unusuable. I do a lot of that work myself, so I'm sensitive to the
> issue.
>
> I'm currently working on building the new hydra.gnu.org which will
> hopefully perform much better, although we will still need to work
> within our build capacity constraints until we have many more build
> slaves.
As you can see, even with the trimming of unnecessary jobs that I have
already done, Hydra has too much to do and is making very slow progress.
I would like to propose that we merge 'wip-glib' into 'core-updates',
remove the 'wip-glib' branch and jobset, and focus Hydra on building all
of 'core-updates'.
What do you think?
Mark
next prev parent reply other threads:[~2015-04-24 22:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 10:11 [PATCH 1/7] gnu: gobject-introspection: Update to 1.44.0 宋文武
2015-04-20 10:11 ` [PATCH 2/7] gnu: itstool: Update to 2.0.2 宋文武
2015-04-20 10:11 ` [PATCH 3/7] gnu: dbus-glib: Update to 0.104 宋文武
2015-04-20 10:11 ` [PATCH 4/7] gnu: libsigc++: Update to 2.4.1 宋文武
2015-04-20 10:11 ` [PATCH 5/7] gnu: glibmm: Update to 2.44.0 宋文武
2015-04-20 10:12 ` [PATCH 6/7] gnu: python-pygobject: Update to 3.16.1 宋文武
2015-04-20 10:12 ` [PATCH 7/7] gnu: poppler: Update to 0.32.0 宋文武
2015-04-21 21:04 ` [PATCH 1/7] gnu: gobject-introspection: Update to 1.44.0 Ludovic Courtès
2015-04-22 2:03 ` 宋文武
2015-04-21 21:05 ` Ludovic Courtès
2015-04-21 21:15 ` Andreas Enge
2015-04-21 22:18 ` Mark H Weaver
2015-04-22 2:06 ` 宋文武
2015-04-22 12:06 ` Andreas Enge
2015-04-22 15:03 ` Mark H Weaver
2015-04-22 15:54 ` Andreas Enge
2015-04-22 21:00 ` Ludovic Courtès
2015-04-22 21:23 ` Mark H Weaver
2015-04-24 22:22 ` Mark H Weaver [this message]
2015-04-25 9:00 ` Mark H Weaver
2015-04-25 18:41 ` Andreas Enge
2015-04-26 0:00 ` 宋文武
2015-04-26 9:36 ` Andreas Enge
2015-04-26 14:07 ` Andreas Enge
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fv7pyxna.fsf@netris.org \
--to=mhw@netris.org \
--cc=andreas@enge.fr \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).