unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Staging freeze
Date: Thu, 29 Dec 2016 13:42:41 -0500	[thread overview]
Message-ID: <20161229184241.GB23768@jasmine> (raw)
In-Reply-To: <87d1gafwst.fsf@gnu.org>

On Thu, Dec 29, 2016 at 06:51:46PM +0100, Ludovic Courtès wrote:
> Hi!
> 
> John Darrington <john@darrington.wattle.id.au> skribis:
> 
> > For what it's worth, I find that building *anything* related to qemu fails
> > for different reasons in about 2/3 attempts. So I think there is a 
> > fundamental, yet to be diagnosed problem.
> 
> Yet to be diagnosed… and yet to be reported?  :-)
> 
> This ‘qemu-image’ job has been failing since Dec. 11, apparently because
> the closure of the OS in build-aux/hydra/demo-os.scm has become more
> than 1.4G (the size specified in build-aux/hydra/gnu-system.scm):
> 
>   https://hydra.gnu.org/job/gnu/master/qemu-image.x86_64-linux
> 
> I’m tempted to simply remove this job because it doesn’t buy us anything
> compared to the system tests.

Okay!

> Objections?

None here :)

  reply	other threads:[~2016-12-29 18:42 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-23  5:23 Staging freeze Leo Famulari
2016-12-23  6:00 ` John Darrington
2016-12-26 18:16   ` Leo Famulari
2016-12-27 23:56 ` Leo Famulari
2016-12-28  4:13   ` Leo Famulari
2016-12-28  9:17     ` John Darrington
2016-12-29 17:16       ` Leo Famulari
2016-12-29 17:51       ` Ludovic Courtès
2016-12-29 18:42         ` Leo Famulari [this message]
2016-12-31 11:12           ` Ludovic Courtès
2017-01-04  8:45 ` Leo Famulari
2017-01-04 22:31   ` Ludovic Courtès
2017-01-07 11:50     ` Let’s fix build failures on ‘staging’! Ludovic Courtès
2017-01-07 17:15       ` Fix python-pygpgme FTBFS [was Re: Let’s fix build failures on ‘staging’!] Leo Famulari
2017-01-07 21:31         ` Ludovic Courtès
2017-01-07 21:46           ` Leo Famulari
2017-01-07 17:22       ` Let’s fix build failures on ‘staging’! Leo Famulari
2017-01-07 17:35       ` Leo Famulari
2017-01-07 21:32         ` Ludovic Courtès
2017-01-07 21:46           ` Leo Famulari
2017-01-08 17:19       ` Leo Famulari
2017-01-07 18:10     ` [PATCH 1/2] Revert "gnu: Add threaded variants of fftw and fftwf for Ardour and mod-host." David Craven
2017-01-07 18:10       ` [PATCH 2/2] gnu: ardour: Add eudev dependency David Craven
2017-01-07 19:11       ` [PATCH 1/2] Revert "gnu: Add threaded variants of fftw and fftwf for Ardour and mod-host." Ricardo Wurmus
2017-01-07 22:43         ` David Craven
2017-01-07 22:45           ` David Craven
2017-01-08 10:57             ` Ludovic Courtès
2017-01-08  7:23           ` Ricardo Wurmus
  -- strict thread matches above, loose matches on Subject: below --
2020-10-13 21:54 staging freeze Marius Bakke
2020-10-13 21:57 ` Julien Lepiller
2020-10-13 22:28   ` Marius Bakke
2020-10-15 12:33 ` zimoun

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=20161229184241.GB23768@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).