| 9 Sep 2021 |
 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 |
| sterni | In reply to @trofi:matrix.org
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? restart should propagate to reverse dependencies (in basically all cases?) imo, would be a nice quality of life feature | 18:41:05 |
| 13 Sep 2021 |
|  Florian | W3F - OoO Mon/Tue changed their display name from Florian | W3F - OoO to Florian | W3F - OoO Mon/Tue. | 11:56:28 |
| 14 Sep 2021 |
|  moritz.hedtke joined the room. | 17:15:02 |
|  Rev. CornWallace III (sun/tzu) changed their display name from cw (novus ordo seclorum) to Fauci's Fine Wines. | 21:35:04 |
| Rev. CornWallace III (sun/tzu) changed their display name from Fauci's Fine Wines to Corn Wallet. | 21:35:38 |
| 15 Sep 2021 |
|  jbedo joined the room. | 04:00:52 |
| jbedo changed their display name from vk3wtf to jbedo. | 04:01:02 |
 mbprtpmnr | I have a question if someone can help me... Is possible to make an Hydra job to build my system flake configuration? | 05:52:23 |
 tomberek | set a hydraJob in your flake to your system configuration | 06:37:53 |
| mbprtpmnr | In reply to @tomberek:matrix.org
set a hydraJob in your flake to your system configuration Can you please show me an example if you want? | 07:06:49 |
| tomberek | you'd set something like hydraJob.mySystem.x86_64-linux = self.nixosConfigurations.tframe.config.system.build.toplevel | 07:20:18 |
| mbprtpmnr | `mySystem` is actual my hostname, right? | 07:25:49 |
| mbprtpmnr | * ```mySystem``` is actual my hostname, right? | 07:26:05 |
| mbprtpmnr | * `mySystem` is actual my hostname, right? | 07:26:14 |
| mbprtpmnr | * mySystem is actual my hostname, right? | 17:21:45 |
| 16 Sep 2021 |
| tomberek | that would be the name of the hydra job. in this example "tframe" is the hostname. | 01:01:50 |
| Rev. CornWallace III (sun/tzu) changed their display name from Corn Wallet to CornWallace. | 01:56:38 |
