| 8 Sep 2021 |
 das_j | Ah, learned something new today ;) | 19:59:10 |
 lukegb (he/him) | https://hydra.nixos.org/static/js/common.js basically, you should be able to click on the sticky-out-bit of the line next to each thing to expand/collapse it | 19:59:36 |
| lukegb (he/him) | maybe you're right and it never worked, though | 20:00:12 |
 Rick (Mindavi) | Someone was working on a pr to make it collapsible | 20:00:47 |
 ajs124 | das_j our version might just be too old for that feature | 20:00:58 |
| das_j | oh | 20:01:07 |
| Rick (Mindavi) | This one: https://github.com/NixOS/hydra/pull/906 | 20:02:14 |
| das_j | feels like someone could just replace the `$(document).ready by something that is triggered when the tree is loaded (→ when the spinner is replaced) | 20:02:51 |
| das_j | * feels like someone could just replace the $(document).ready( by something that is triggered when the tree is loaded (→ when the spinner is replaced) | 20:02:58 |
 tomberek | my approach tries to use HTML summary/details as the mechanism to have toggled build trees | 21:26:09 |
| 9 Sep 2021 |
|  trofi joined the room. | 08:37:54 |
| trofi | Basic hydra UI question: https://hydra.nixos.org/jobset/nixpkgs/binutils-2.36 shows 4 build jobs that are queued for more than 2 weeks. Are they really queued for that long or it's an artifact of some cancellation? | 08:39:42 |
| Rick (Mindavi) | I'd say that they're still queued | 08:52:32 |
| das_j | Yes, cancelling builds removes from the list them iirc | 08:54:01 |
| das_j | * Yes, cancelling builds removes them from the list iirc | 08:54:05 |
| Rick (Mindavi) | Yeah, they get the status 'aborted' | 08:55:28 |
| trofi | Aha. If I look at specific examples at https://hydra.nixos.org/eval/1698592#tabs-unfinished I see that one of the dependencies is timed out: https://hydra.nixos.org/build/150507932#tabs-buildsteps. I would naively expect it to fail the queued job. Or there is a retry somewhere? | 09:53:03 |
| trofi | Best I cloud find is https://discourse.nixos.org/t/finding-most-depended-upon-packages-that-fail-to-build-in-hydra/10090/2 which fetches build logs one by one and parses HTML. Not very light for a casual run. | 21:56:10 |
| trofi | Filed https://github.com/NixOS/hydra/issues/1018 | 22:25:19 |
 sterni | I'd expect that such queries would be much to expensive to be something you can actually expose to users | 22:39:55 |
| sterni | (although you can always rework the database if you really want to) | 22:40:24 |
| 10 Sep 2021 |
 @grahamc:nixos.org | notably none of that strictly needs to query hydra | 01:13:58 |
| @grahamc:nixos.org | almost none | 01:14:06 |
| @grahamc:nixos.org | like, the client itself could do the evaluation and check the cache to identify popular missing store paths from the cache | 01:14:27 |
| trofi | grahamc (he/him): should I close it and file against nix (or maybe nixpkgs)? | 06:26:59 |
| 11 Sep 2021 |
| trofi | Another hydra question: suppose build failed for transient reasons and hydra marks build as broken (running example is llvm_10 in nixpkgs:master that failed 12 days ago: https://hydra.nixos.org/build/151485978). When will hydra try to rebuild it again? Only when derivation changes? Or there is an expiration built in as well? | 17:05:46 |
| Rick (Mindavi) | Only when derivation or one of the inputs change, or someone restart manually (afaik) | 17:13:15 |
 cransom | it won't automatically retry. inputs for the derivation would need to change, or someone can hit the retry button if they have privileges. | 17:29:55 |
| cransom | (as rick said) | 17:30:10 |
| * lukegb (he/him) presses the retry button | 18:34:14 |
