all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Cuirass: "lint -c archival"?
Date: Thu, 24 Sep 2020 12:29:33 +0200	[thread overview]
Message-ID: <CAJ3okZ3b6d8qvgM_m51nJ7A00PpoQrEod3M-kPgvv5zMZqq+mw@mail.gmail.com> (raw)
In-Reply-To: <87k0wj7hw1.fsf@gnu.org>

Hi,

On Thu, 24 Sep 2020 at 09:28, Mathieu Othacehe <othacehe@gnu.org> wrote:

> > The idea behind is then to ask SWH folks to increase the rate limit
> > for a specific IP (or couple of IPs).  Today, the SWH rate is 10 save
> > requests per hour, i.e., 240 per day (more or less).  And the new
> > chart [1] shows that there are ~2000 builds per day.  Ouch! :-)
>
> Yesterday almost 18.000 derivations were added, and even if only 10.000
> were built, it is indeed quite substantial.

That's good news. :-)

On average, it is ~2000, right?

Well, we could set a limit for the extra days, sending the X first
buildings where X is in agreement with SWH.
It would be far from perfect and some packages would not be saved, but
it seems better than the current situation (depends on the
submitter/reviewer only).

This would be something in the meantime; while waiting the SWH
sources.json loads accepts more than 'url-fetch' sources.


> > If it is not possible, then instead does it make sense to add a script
> > to etc/?  If SWH accepts to increase the rate for a specific machine,
> > the script (fold-packages+save-origin) could run with some delay and
> > save all the missing Git references.
>
> Adding some sort of "post build" hook to Cuirass that would trigger an
> SHW archival would be possible, even though it would require to
> implement this mechanism.

Cool!  Yakafonkon. ;-)

> Having a cron job archiving missing references would also be possible I
> guess, but I may have a preference for the first option.

Because I am lazy, the "post build" hook appears to me more
complicated to implement than a cron job with a Scheme script (that I
almost already have :-)).  Hey, "Now is better than never. Although
never is often better than *right* now." :-)


Thanks,
simon


  reply	other threads:[~2020-09-24 10:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-23 16:58 Cuirass: "lint -c archival"? zimoun
2020-09-24  7:28 ` Mathieu Othacehe
2020-09-24 10:29   ` zimoun [this message]
2020-09-24 19:06 ` Christopher Baines
2020-09-25  8:56   ` Automation of SWH save (was: Cuirass: "lint -c archival"?) 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

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

  git send-email \
    --in-reply-to=CAJ3okZ3b6d8qvgM_m51nJ7A00PpoQrEod3M-kPgvv5zMZqq+mw@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=othacehe@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.