GNU bug report logs - #27876
[PATCH] cuirass: add Hydra compatible HTTP API.

Previous Next

Package: guix-patches;

Reported by: Mathieu Othacehe <m.othacehe <at> gmail.com>

Date: Sun, 30 Jul 2017 10:09:01 UTC

Severity: normal

Tags: patch

Done: Mathieu Othacehe <m.othacehe <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


Message #46 received at 27876-done <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Mathieu Othacehe <m.othacehe <at> gmail.com>
Cc: 27876-done <at> debbugs.gnu.org
Subject: Re: [bug#27876] [PATCH v2 1/3] cuirass: Store new information in
 database to prepare new HTTP API integration.
Date: Sun, 10 Sep 2017 15:01:27 +0200
Heya Mathieu,

Mathieu Othacehe <m.othacehe <at> gmail.com> skribis:

>> With an autoincremented index, I suppose we might want to make sure that
>> ‘db-add-build’ does not add a new entry for a build that’s already in
>> the table.  WDYT?
>
> Yes we might, but looking for a build with the same
> derivation-evaluation-outputs before each build insertion will be an
> expensive operation (now that this tuple is no longer the primary key).

OK, but isn’t there a risk of recording the same set of derivations at
every evaluation?

Basically, between two subsequent evaluations, 99% of the derivations
are exactly the same (assuming an evaluation is triggered at each git
push, and each git push adds/modifies just a handful of packages).  If
we record new builds for these 99%, even though nothing has changed,
then that’s potentially bad, no?

Thanks,
Ludo’.




This bug report was last modified 7 years and 259 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.