Tobias Geerinckx-Rice wrote:
(new nar field?)
Actually, that won't work, since NAR URLs are hash-based and we're
hardly interested in packages that do have substitutes available.
One'd have to grow another /api//build-times wart or
something.
Kind regards,
T G-R
signature.asc
Swedebugia, Guix,
I was about to answer on IRC when I saw this thread :-)
swedebugia wrote:
Maybe we could have an additional time measurement:
Ghzminutes. E.g. if the build took 60 minutes on a 3 Ghz machine
it
took 20 Ghzminutes.
The build node would have to communicate the total
Ghz
swedebugia transcribed 385 bytes:
> Hi
>
> On 2019-06-21 18:01, Andreas Enge wrote:
> > On Fri, Jun 21, 2019 at 05:43:54PM +0200, swedebugia wrote:
> > > Maybe we could have an additional time measurement:
> > > Ghzminutes.
> > > E.g. if the build took 60 minutes on a 3 Ghz machine it took 20
Hi
On 2019-06-21 18:01, Andreas Enge wrote:
On Fri, Jun 21, 2019 at 05:43:54PM +0200, swedebugia wrote:
Maybe we could have an additional time measurement: Ghzminutes.
E.g. if the build took 60 minutes on a 3 Ghz machine it took 20 Ghzminutes.
180 GHzmin?
Yes, thanks for correcting me!
On Fri, Jun 21, 2019 at 05:43:54PM +0200, swedebugia wrote:
> Maybe we could have an additional time measurement: Ghzminutes.
> E.g. if the build took 60 minutes on a 3 Ghz machine it took 20 Ghzminutes.
180 GHzmin?
Andreas
Hi
I would like to estimate how long building the rust toolchain would take
on my 2-c 2.2 Ghz laptop.
I asked on irc and had an idea of improvement:
swedebugia: you can check the build duration for past builds
on ci.guix.gnu.org
most of the build nodes are pretty old and weak, though
