Luke Granger-Brown 67ebce8493 Output evaluation errors without crashing if aggregate job is broken. ... At the moment, aggregate jobs can easily break and cause the entire evaluation to fail, which is not ideal. For Nixpkgs, we do have some important aggregate jobs (like `tested`), but for debugging and building purposes it's still useful to get a partial result even if the channel won't actually advance. This commit changes the behaviour of hydra-eval-jobs such that it aggregates any errors found during the construction of an aggregate, and will instead annotate the job with the evaluation failure such that it shows up in a "cleaner" way. There are really two types of failure that we care about: one is where the attribute just ends up missing altogether in the final output, and also where the attribute is in the output but fails to evaluate. Both are handled here. Note that this does mean that the same error message may be output multiple times, but this aids debuggability because it'll be much clearer what's blocking the job from being created.		2021-10-26 10:14:34 +01:00
..
hydra-eval-jobs.cc	Output evaluation errors without crashing if aggregate job is broken.	2021-10-26 10:14:34 +01:00
Makefile.am	Fix build	2020-06-23 13:56:44 +02:00