From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from re-prd-fep-042.btinternet.com (mailomta8-re.btinternet.com [213.120.69.101]) by sourceware.org (Postfix) with ESMTPS id 247273858C74 for ; Mon, 20 Mar 2023 11:22:27 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 247273858C74 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=dronecode.org.uk Authentication-Results: sourceware.org; spf=none smtp.mailfrom=dronecode.org.uk Received: from re-prd-rgout-004.btmx-prd.synchronoss.net ([10.2.54.7]) by re-prd-fep-042.btinternet.com with ESMTP id <20230320112225.TVHA30996.re-prd-fep-042.btinternet.com@re-prd-rgout-004.btmx-prd.synchronoss.net>; Mon, 20 Mar 2023 11:22:25 +0000 Authentication-Results: btinternet.com; auth=pass (PLAIN) smtp.auth=jonturney@btinternet.com; bimi=skipped X-SNCR-Rigid: 63FE9A2B022E2EC8 X-Originating-IP: [81.153.98.181] X-OWM-Source-IP: 81.153.98.181 (GB) X-OWM-Env-Sender: jonturney@btinternet.com X-VadeSecure-score: verdict=clean score=0/300, class=clean X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgedvhedrvdefkedgvdeiucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuueftkffvkffujffvgffngfevqffopdfqfgfvnecuuegrihhlohhuthemuceftddunecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtkeertddtfeejnecuhfhrohhmpeflohhnucfvuhhrnhgvhicuoehjohhnrdhtuhhrnhgvhiesughrohhnvggtohguvgdrohhrghdruhhkqeenucggtffrrghtthgvrhhnpedvtdetffekveevjeegheeglefhtdeggfeilefggfdutedufedvgefgieeiffdtveenucfkphepkedurdduheefrdelkedrudekudenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhephhgvlhhopegludelvddrudeikedruddruddtiegnpdhinhgvthepkedurdduheefrdelkedrudekuddpmhgrihhlfhhrohhmpehjohhnrdhtuhhrnhgvhiesughrohhnvggtohguvgdrohhrghdruhhkpdhnsggprhgtphhtthhopedvpdhrtghpthhtoheptgihghifihhnqdgrphhpshestgihghifihhnrdgtohhmpdhrtghpthhtohepkhgsrhhofihnsegtohhrnhgvlhhlrdgvughupdhrvghvkffrpehhohhsthekuddqudehfedqleekqddukedurdhrrghnghgvkeduqdduheefrdgsthgtvghnthhrrghlphhluhhsrdgtohhmpdgruhhthhgpuhhsvghrpehjohhnthhurhhnvgihsegsthhinhhtvghrnhgvthdrtghomhdp ghgvohfkrfepifeupdfovfetjfhoshhtpehrvgdqphhrugdqrhhgohhuthdqtddtge X-RazorGate-Vade-Verdict: clean 0 X-RazorGate-Vade-Classification: clean Received: from [192.168.1.106] (81.153.98.181) by re-prd-rgout-004.btmx-prd.synchronoss.net (5.8.814) (authenticated as jonturney@btinternet.com) id 63FE9A2B022E2EC8; Mon, 20 Mar 2023 11:22:25 +0000 Message-ID: <7f34bc2b-fac3-27f8-e8ae-3a9f452ee51c@dronecode.org.uk> Date: Mon, 20 Mar 2023 11:22:25 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.9.0 Subject: Re: How to avoid tying up scallywag To: Ken Brown , "cygwin-apps@cygwin.com" References: <8ffc47a4-1004-002b-c81f-6cafa7076f95@cornell.edu> Content-Language: en-GB From: Jon Turney In-Reply-To: <8ffc47a4-1004-002b-c81f-6cafa7076f95@cornell.edu> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1191.2 required=5.0 tests=BAYES_00,FORGED_SPF_HELO,KAM_DMARC_STATUS,KAM_LAZY_DOMAIN_SECURITY,NICE_REPLY_A,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_NONE,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: 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.