GNU bug report logs - #22078
failed builds due to exceeding max-silent-time not marked as failed in db

Previous Next

Full log

View this message in rfc822 format

From: ludo <at> gnu.org (Ludovic Courtès)
To: Florian Paul Schmidt <mista.tapas <at> gmx.net>
Cc: 22078 <at> debbugs.gnu.org
Subject: bug#22078: failed builds due to exceeding max-silent-time not marked as failed in db
Date: Mon, 14 Dec 2015 00:11:23 +0100

Florian Paul Schmidt <mista.tapas <at> gmx.net> skribis:

> Attached is a first stab at fixing this. There are additional options
> to guix-daemons now:
>
>       --cache-failures       cache build failures
>       --cache-hook-failures  cache build failures due to hook failures
> (depends
>                              on cache-failures)
>       --cache-timeout-failures   cache build failures due to timeouts
> (depends
>                              on cache-failures)

OK.  I’m unsure whether it makes sense to cache failures due to timeout
because, by definition, they’re non-deterministic.

Another problem is that clients can choose what the timeout is (both
max-silent-time and absolute max-time), so it’d be easy for a client to
force a timeout failure; on a multi-user system, that would amount to a
DoS attack.

I’m not sure how to address these issues, so I’m rather in favor of the
status quo.

WDYT?

Thanks,
Ludo’.

Previous Next

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