unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: brice@waegenei.re
Cc: guix-devel@gnu.org, guix-sysadmin@gnu.org
Subject: Re: Hundreds of failed build on master following git package update
Date: Tue, 17 Aug 2021 22:32:24 +0100	[thread overview]
Message-ID: <87h7fnhi53.fsf@cbaines.net> (raw)
In-Reply-To: <3519-611c1b00-cb-54469d80@34457950>

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


brice@waegenei.re writes:

> Today I pushed 2 commits¹ related to the package to master, mainly to
> update it to 2.33.0. But since then https://data.guix.gnu.org/ went
> offline and Cuirass' evaluation #4930² has 556 failed build. Newly
> failed builds have unhelpful logs, ending with "cannot build missing
> derivation [...]"³.
>
> Before pushing those commits, I build git and git-minimal successfully
> on x86_64 and assessed the total impacted package for this update to
> be inferior to 300. Did I do something wrong with the update commit?
> Or is it an unrelated issue?

Hey,

Thanks for noticing that data.guix.gnu.org was down. I've had a look,
and the machine that runs it ran out of disk space.

I'm not quite sure why it ran out of disk space, I suspect it was maybe
excessive PostgreSQL logs... anyway, I'll get things going again and
keep an eye on it.

Once data.guix.gnu.org has caught up it will be easier to see what the
impact of this change is. I don't have any reason to think it was wrong
to make these changes.

Thanks,

Chris

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

  reply	other threads:[~2021-08-17 21:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-17 20:24 Hundreds of failed build on master following git package update brice
2021-08-17 21:32 ` Christopher Baines [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-08-17 21:13 Sarah Morgensen
2021-08-18  7:11 ` Mathieu Othacehe

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=87h7fnhi53.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=brice@waegenei.re \
    --cc=guix-devel@gnu.org \
    --cc=guix-sysadmin@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).