From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Jacob Hrbek <kreyren@rixotstudio.cz>,
Vagrant Cascadian <vagrant@debian.org>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Proposal: Build timers
Date: Thu, 25 Nov 2021 06:21:21 +0100 [thread overview]
Message-ID: <65a9fc45a222d0148e3b109c834de9c9b9151086.camel@gmail.com> (raw)
In-Reply-To: <fBaqTTKqq9VHjnszAyJdxF5WVBKclPR4n9qH-8U4tEeq1AF8dgLCEL9m38ALOPvXk4b5ttYbqamC3hOVAUrEcMnh3k0jwcy4ihZeJIhvXsc=@rixotstudio.cz>
Am Donnerstag, den 25.11.2021, 04:03 +0000 schrieb Jacob Hrbek:
> Make it clear it's an estimate, or maybe even abstract away the time
> units so that there is no expectation of any particular time. --
> Vagrant
>
> My theory is designed with tolerance of <5 min with max tolerance of
> =10 min with methods that I am confident will get us within <30 sec
> assuming sufficient amount of data to construct the variables.
You are courageous to assume a variance of 5 minutes, let alone 30
seconds in everyday systems. Aside from the variables I've already
pointed out, you'd have to consider that certain builds outside of CI
will enter a state of constant swapping at some point, yet still finish
building if not hitting OOM limits. Also the fact that Guix might not
be the only process hogging resources on some particular machine.
next prev parent reply other threads:[~2021-11-25 5:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 22:02 Proposal: Build timers Jacob Hrbek
2021-11-23 1:06 ` zimoun
2021-11-23 6:21 ` Jacob Hrbek
2021-11-23 11:56 ` zimoun
2021-11-23 14:39 ` Jacob Hrbek
2021-11-24 11:35 ` zimoun
2021-11-25 4:00 ` Jacob Hrbek
2021-11-23 12:05 ` Julien Lepiller
2021-11-23 16:23 ` zimoun
2021-11-23 20:09 ` Liliana Marie Prikler
2021-11-23 21:31 ` Jacob Hrbek
2021-11-23 21:35 ` Jacob Hrbek
2021-11-23 23:50 ` Julien Lepiller
2021-11-24 11:31 ` zimoun
2021-11-24 20:23 ` Vagrant Cascadian
2021-11-24 21:50 ` zimoun
2021-11-25 4:03 ` Jacob Hrbek
2021-11-25 5:21 ` Liliana Marie Prikler [this message]
2021-11-25 10:23 ` 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=65a9fc45a222d0148e3b109c834de9c9b9151086.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=guix-devel@gnu.org \
--cc=kreyren@rixotstudio.cz \
--cc=vagrant@debian.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).