| 25 Sep 2024 |
 K900 | Yeah that's by job ID | 13:15:34 |
| K900 | Which is the number | 13:15:37 |
 @rick:matrix.ciphernetics.nl | #💡 the hydra endpoint /{project-id}/{jobset-id}/{job-id}/latest (as documented here: https://github.com/NixOS/hydra/issues/1036) will return the latest _working_ build for a job! This makes it very easy to see how long a job has been broken already. | 13:15:41 |
| K900 | I think | 13:15:51 |
| @rick:matrix.ciphernetics.nl | I think so, yeah | 13:16:59 |
| @rick:matrix.ciphernetics.nl | I'm at least aware there are some gaps where you'd expect endpoints so it's likely the one you want is missing | 13:17:53 |
| @rick:matrix.ciphernetics.nl | I ran into that too while building that script | 13:17:59 |
| @rick:matrix.ciphernetics.nl | Still hoping for someone adding those endpoints, but I presume it'll be rewritten before those are added 😅. I looked at the perl but already didn't understand the existing endpoints, let alone adding some | 13:21:45 |
 @asymmetric:matrix.dapp.org.uk | where are endpoints defined in the code? | 13:56:30 |
| @asymmetric:matrix.dapp.org.uk | also, under what conditions are logs a 404? e.g. for this build failure, no logs are available: https://hydra.nixos.org/build/271530024 | 13:57:04 |
| K900 | Because > Cancelled by user | 13:57:30 |
| K900 | There was no build to begin with | 13:57:33 |
| @asymmetric:matrix.dapp.org.uk | ah right, just saw that after asking, thx | 13:57:52 |
| @asymmetric:matrix.dapp.org.uk | just for context i'm thinking of building a matrix bot that periodically fetches job pages for selected packages, and notifies subscribers in case of failures | 13:59:17 |
| @rick:matrix.ciphernetics.nl | Make sure to rate-limit your bot. Maybe the nixpkgs-review-tools data is public? | 15:02:22 |
| @rick:matrix.ciphernetics.nl | Would be great if we could not all scrape hydra 😁 | 15:02:39 |
| @rick:matrix.ciphernetics.nl | I managed to get myself blocked for a short while by overloading hydra | 15:03:04 |
| 26 Sep 2024 |
|  Fabián Heredia set a profile picture. | 01:16:06 |
| 27 Sep 2024 |
|  SigmaSquadron joined the room. | 00:18:20 |
| @asymmetric:matrix.dapp.org.uk | re: this: https://github.com/NixOS/hydra/blob/95003f2eb503f71979856470c7caea946f1ae7f0/doc/manual/src/notifications.md
is this hydra-notify component deployed on prod hydra? are any plugins enabled? i tried looking here for hints, it seems it is deployed but
a) idk if hydra-dev is actually prod
b) whether any plugins are configured
c) whether there's any interest on the infra people's side to deploy one for build notifications
| 08:43:42 |
| K900 | It's deployed but turned off | 08:44:00 |
| K900 | And the reason it's turned off is because it takes up stupid amounts of RAM and no one has figured out why | 08:44:14 |
| K900 | (or as far as I can tell attempted to) | 08:44:18 |
| K900 | And that machine is already severely RAM starved | 08:44:45 |
| K900 | Because it is running nixpkgs evals | 08:44:50 |
 vcunat | The other reason is that we're not aware of any use for it at hydra.nixos.org | 09:16:32 |
| K900 | Honestly I don't think anyone would have cared about it | 09:17:22 |
| K900 | If it didn't use half the RAM on the box | 09:17:26 |
| @asymmetric:matrix.dapp.org.uk | In reply to @vcunat:matrix.org
The other reason is that we're not aware of any use for it at hydra.nixos.org wouldn't it be useful for notifying maintainers of build failures, with mechanisms other than email? | 13:13:35 |
| vcunat | Probably. But I believe there's no code for that. Even this code was unreliable, sending mass notifications in some edge cases IIRC. | 13:46:04 |
