| 13 Nov 2023 |
 K900 | And most of those are expected failures because of unfree licenses or packages marked broken | 17:48:53 |
| K900 | Also, ZHF doesn't literally mean "reach 0 failures or die", and it doesn't mean "nothing is marked broken" | 17:49:12 |
 Philip Taron (UTC-8) | Thanks, K900 ⚡️ . Is there a way to cause Hydra to "triage" known evaluation errors so that "real" evaluation errors are highlighted? | 17:51:24 |
| K900 | Generally, "everything that should eval evals" is ~enforced by ofborg | 17:51:48 |
| K900 | So it's not something you need to look at closely | 17:52:08 |
| Philip Taron (UTC-8) | Got it. I'll direct my attention elsewhere. Thanks for the information! | 18:06:37 |
| 14 Nov 2023 |
|  @vyls:matrix.org left the room. | 18:21:23 |
| @vyls:matrix.org joined the room. | 18:21:32 |
| @vyls:matrix.org left the room. | 18:22:26 |
| 15 Nov 2023 |
|  Marius joined the room. | 13:45:07 |
| Marius | Hello. I set up an Hydra server for doing some custom CI of a package manager (portmod), and I had a wrongly written fetch script for a fixed output derivation. I now fixed it, but Hydra doesn’t re-evaluate it (certainly cause the result set end up having the same hash). Is there some way I can force it rebuild all failed derivation according to a new definition even if the hash is identical?
(I already had this problem once, and it seems changing the hash of the dependant and re-evaluating wasn’t enought, but I had to change the name anyway, which resulted in a different hash and so a rebuild) | 14:47:28 |
| Marius | * Hello. I set up an Hydra server for doing some custom CI of a package manager (portmod), and I had a wrongly written fetch script for a fixed output derivation. I now fixed it, but Hydra doesn’t re-evaluate it (certainly cause the result set end up having the same hash). Is there some way I can force it to rebuild all failed derivation according to a new definition even if the result set hash is identical?
(I already had this problem once, and it seems changing the hash of the dependant and re-evaluating wasn’t enought, but I had to change the name anyway, which resulted in a different hash and so a rebuild for every sources) | 14:52:08 |
|  @grahamc:nixos.orgchanged room power levels. | 15:54:41 |
| @grahamc:nixos.org left the room. | 15:54:41 |
|  Alyssa Ross | 17:09:00 |
|  NixOS Moderation Botchanged room power levels. | 18:12:00 |
| NixOS Moderation Botchanged room power levels. | 18:12:00 |
|  @eisfunke:eisfunke.com changed their profile picture. | 22:42:14 |
| 17 Nov 2023 |
|  @yuri:nekover.se changed their display name from yuri to fi (she/her). | 01:44:16 |
 Arian | Are there docs for Hydra anywhere ? | 13:10:57 |
| Arian | https://nixos.org/hydra/manual/ just downloads a partial corrupted html file | 13:11:06 |
 Julien | Code source is the documentation right ? | 13:17:03 |
| Julien | That being said the link you just sent works for me | 13:17:30 |
| Julien | It redirects to https://hydra.nixos.org/build/196107287/download/1/hydra/introduction.html | 13:17:36 |
| Arian | which on safari just causes a download due to lacking Content-Typehe ader | 13:18:04 |
| Arian | also for me the CSS is broken | 13:18:11 |
| Julien | On what ? :p | 13:18:29 |
| Arian | on chromium the CSS is broken | 13:18:38 |
| Arian | 
Download image.png | 13:18:58 |
| Julien | Strange | 13:22:38 |
