Maximilian Bosch 9b465e7a67 Make "timed out" and "log limit exceeded" builds aborted ... In 73694087a0 I gave builds that failed because of a timeout or exceeded log limit a stop sign and I stand by that reasoning: with that it's possible to distinguish between actual build failures and rather transient things such as timeouts. Back then I considered it a feature that these are shown in a different tab, but I don't think that's a good idea anymore. When using a jobset to e.g. track the regressions from a mass rebuild (like a compiler or gcc update), "Newly failed builds" should exclusively display regressions (and flaky builds of course, not much I can do about that). Also, when a bunch of builds fail in such a jobset because of e.g. a broken connection to a builder that results in a timeout, I want to be able to restart them all w/o rebuilding actual regressions. To make it clear that we not only have "Aborted" builds in the tab, I renamed the label to "Aborted / Timed out".		2024-03-16 22:10:40 +01:00
..
hydra-eval-jobs	More CA derivations prep	2024-01-25 21:32:22 -05:00
hydra-evaluator	Update to Nix 2.19	2023-11-30 15:26:46 -05:00
hydra-queue-runner	hydra-queue-runner: drop broken connections from pool	2024-03-16 22:10:40 +01:00
lib	Make "timed out" and "log limit exceeded" builds aborted	2024-03-16 22:10:40 +01:00
libhydra	Update to Nix 2.19	2023-11-30 15:26:46 -05:00
root	Make "timed out" and "log limit exceeded" builds aborted	2024-03-16 22:10:40 +01:00
script	More CA derivations prep	2024-01-25 21:32:22 -05:00
sql	Add migration to drop non-null constraints	2024-01-26 11:53:58 -05:00
ttf	Add font for the captcha	2013-03-04 12:16:13 +01:00
Makefile.am	Revert "hydra-eval-jobs -> nix eval-hydra-jobs"	2020-02-19 20:36:52 +01:00
Makefile.PL	perlcritic: use strict, use warnings	2021-09-06 22:13:33 -04:00