Re: [PATCH] sql: Add a couple of indexes.

[zimoun <zimon.toutoune@gmail.com>]

Hi Chris,

On Sun, 14 Jun 2020 at 12:48, Christopher Baines <mail@cbaines.net> wrote:

>> --8<---------------cut here---------------start------------->8---
>>   65.7% substitutes available (9,425 out of 14,354)
>>   at least 57,816.3 MiB of nars (compressed)
>>   97,343.9 MiB on disk (uncompressed)
>>   0.010 seconds per request (138.1 seconds in total)
>>   103.0 requests per second
>>
>>   0.0% (0 out of 4,929) of the missing items are queued
>>   at least 1,000 queued builds
>>       x86_64-linux: 1000 (100.0%)
>>   build rate: 9.20 builds per hour
>>       x86_64-linux: 9.20 builds per hour
>> --8<---------------cut here---------------end--------------->8---
>>
>> Hum?  Almost 1/3 of substitutes are not available and in the same time
>> not queued.  Is it expected?  Does it mean that 1/3 of the builds are
>> failing?
>
> Probably not, most likely canceled or a dependency failed to build.

Well, it depends on how you define what is a build. ;-) Because if one
package's dependency does not build, the package cannot build either.

I agree that these 1/3 non-available substitutes can be because only one
essential package fails.  We discussed at Guix Days something like "guix
weather --release"; which could help to report what maintainers/developers
consider as essential.

However, I feel that something is lacking to identify which package is
failing and what is its impact.  Something like: the build fails then a
warning is raised if "guix refresh -l" is too high.


Cheers,
simon