From: Jon Turney <jon.turney@dronecode.org.uk>
To: Ken Brown <kbrown@cornell.edu>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: How to avoid tying up scallywag
Date: Mon, 20 Mar 2023 11:22:25 +0000 [thread overview]
Message-ID: <7f34bc2b-fac3-27f8-e8ae-3a9f452ee51c@dronecode.org.uk> (raw)
In-Reply-To: <8ffc47a4-1004-002b-c81f-6cafa7076f95@cornell.edu>
On 19/03/2023 23:04, Ken Brown via Cygwin-apps wrote:
> Jon,
>
> I'll be ready to go with TeX Live 2023 in a couple days. That involves
> about 60 packages. If I push them all at once, I'm afraid that would
> tie up scallywag and make it unusable by others. I was thinking of
> pushing them in batches of 5, with a couple hours in between batches.
> But I don't know how many jobs scallywag can do at once. What do you
> think?
As far as I can tell, the documented limits for the GitHub free service
currently used are currently:
* 20 concurrent jobs
* runs which are queued for more than 45 minutes without starting are
discarded.
The implementation of how the build back-end is used in scallywag is
moderately modularized, so if these restrictions become irksome, and we
ever have access to a better compute service, that could be used instead.
Note that if you are just updating the repository, without using
scallywag to deploy, then pushing with --push-option=nobuild is more
slightly more efficient that SCALLYWAG="nobuild" in the cygport, as it
can short-cut things, since it doesn't need to start a job to evaluate
the tokens to determine if nobuild is set.
next prev parent reply other threads:[~2023-03-20 11:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 23:04 Ken Brown
2023-03-20 3:48 ` marco atzeri
2023-03-20 11:22 ` Jon Turney [this message]
2023-03-20 13:14 ` Ken Brown
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=7f34bc2b-fac3-27f8-e8ae-3a9f452ee51c@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
--cc=kbrown@cornell.edu \
/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.
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).