all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: Dealing with mass rebuilds
Date: Wed, 21 Oct 2015 18:41:51 +0200	[thread overview]
Message-ID: <87wpug9nsg.fsf@gnu.org> (raw)
In-Reply-To: <20151021102706.339f0758@debian-netbook> (Efraim Flashner's message of "Wed, 21 Oct 2015 10:27:06 +0300")

Efraim Flashner <efraim@flashner.co.il> skribis:

> How much build infrastructure does nix have? (do they build all of staging
> all the time?) Would it be possible to identify the subset of packages that
> are immediately dependant on the updated package, and build only those as a
> test on hydra?

‘guix refresh -l’ provides that information.  Hydra itself always tries
to build everything though.

> That would be faster, but if something broke it'd be harder to
> track down, a la 白い熊's conkeror issue.

The Conkeror issue is a run-time issue though, one that is not revealed
by its test suite apparently.

Ludo’.

  reply	other threads:[~2015-10-21 16:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20151020161651.4759.8347@vcs.savannah.gnu.org>
     [not found] ` <E1ZoZal-0001Fl-M5@vcs.savannah.gnu.org>
2015-10-20 18:17   ` 01/01: gnu: curl: Update to 7.45.0 Mark H Weaver
2015-10-20 19:45     ` Dealing with mass rebuilds Ludovic Courtès
2015-10-20 19:56       ` Efraim Flashner
2015-10-20 21:47       ` Andreas Enge
2015-10-21  7:27         ` Efraim Flashner
2015-10-21 16:41           ` Ludovic Courtès [this message]
2015-10-21 16:45         ` Ludovic Courtès
2015-10-22 20:11           ` Paul van der Walt
2015-10-25 21:34             ` Ludovic Courtès
2015-10-22 18:20       ` Mark H Weaver
2015-10-22 18:32         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wpug9nsg.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=efraim@flashner.co.il \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.