From: zimoun <zimon.toutoune@gmail.com>
To: "Guix Devel" <guix-devel@gnu.org>,
"Mathieu Othacehe" <othacehe@gnu.org>,
"Ricardo Wurmus" <rekado@elephly.net>,
"Ludovic Courtès" <ludo@gnu.org>,
"Christopher Baines" <mail@cbaines.net>
Subject: Cuirass: "lint -c archival"?
Date: Wed, 23 Sep 2020 18:58:38 +0200 [thread overview]
Message-ID: <CAJ3okZ29XMSu9e6BDsJsRi4AMD6FpUMt6hwjbHx2d+G9EDabUg@mail.gmail.com> (raw)
Dear,
Does it make sense to add "lint -c archival" when a package is built
by Cuirass? Or on the Guix Data Services?
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! :-)
[1] <https://ci.guix.gnu.org/metrics>
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.
Well, I do not know what the GitLab CI in Bordeaux is doing? About
Guix packages because there are already some things saving requests
automatically, I guess.
WDYT?
All the best,
simon
next reply other threads:[~2020-09-23 16:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 16:58 zimoun [this message]
2020-09-24 7:28 ` Cuirass: "lint -c archival"? Mathieu Othacehe
2020-09-24 10:29 ` zimoun
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
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=CAJ3okZ29XMSu9e6BDsJsRi4AMD6FpUMt6hwjbHx2d+G9EDabUg@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=mail@cbaines.net \
--cc=othacehe@gnu.org \
--cc=rekado@elephly.net \
/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).