| 25 Apr 2024 |
|  @me:indeednotjames.com left the room. | 03:33:20 |
|  @delroth:delroth.net left the room. | 14:43:29 |
|  NixOS Moderation Bot banned  @jonringer:matrix.org (Banned until 2024/06/10 after deliberation of the Moderation team). | 21:11:58 |
|  David Mell (zraexy) joined the room. | 23:19:14 |
| David Mell (zraexy) changed their display name from David Mell to David Mell (zraexy). | 23:51:58 |
| 26 Apr 2024 |
|  @stablejoy:matrix.org changed their profile picture. | 14:03:43 |
|  @patka_123:matrix.org left the room. | 19:33:34 |
| 29 Apr 2024 |
|  stigo left the room. | 12:03:45 |
| NixOS Moderation Botchanged room power levels. | 15:29:48 |
| 30 Apr 2024 |
|  ondt joined the room. | 22:21:41 |
| 1 May 2024 |
| NixOS Moderation Botchanged room power levels. | 15:06:26 |
| 3 May 2024 |
 John Ericson | https://hydra.ngi0.nixos.org/build/3992#tabs-summary I was trying to figure out why this stuff is stuck in queue | 18:03:13 |
| John Ericson | anyone know where to look? | 18:03:16 |
| 4 May 2024 |
|  Regnat left the room. | 15:55:58 |
| 6 May 2024 |
|  tracteur joined the room. | 21:58:35 |
| 7 May 2024 |
 hacker1024 | How do you handle garbage collection when using an S3 store_uri? Is hydra-s3-backup-collect-garbage appropriate? It's made for the S3 backup plugin, which was made before Nix supported S3 natively and (as far as I can tell) is now redundant. | 23:59:52 |
| 12 May 2024 |
|  @man2dev:fedora.im left the room. | 10:22:13 |
| 13 May 2024 |
|  Arian left the room. | 17:44:14 |
| 14 May 2024 |
|  infinisil changed their profile picture. | 17:45:10 |
| 15 May 2024 |
|  raghavsood joined the room. | 08:28:11 |
| raghavsood set a profile picture. | 08:38:29 |
 hexa | is there a requirement for hydra-notify to be up for evaluating/scheduling/shipping builds? | 10:04:58 |
| hexa | wondering if disabling it would impact the hydra.nixos.org pipeline | 10:05:40 |
| hexa | reason is that the service sits at 45 GB of memory usage and evals are getting oom-killed | 10:06:04 |
 @lotte:chir.rs | In reply to @hexa:lossy.network
is there a requirement for hydra-notify to be up for evaluating/scheduling/shipping builds? hydra-notify can be down but stuff like runcommand hooks, github status checks, and log compression will not work | 10:13:19 |
| @lotte:chir.rs | in my experience | 10:13:24 |
| @lotte:chir.rs | hydra-evaluator schedules evaluations, and hydra-queue-runner schedules builds | 10:14:41 |
| @lotte:chir.rs | In reply to @lotte:chir.rs
hydra-notify can be down but stuff like runcommand hooks, github status checks, and log compression will not work of course the runcommand hook is probably where you're shipping the build, unless you use an s3 bucket as a backing store for hydra | 10:15:19 |
| hexa | it's s3 | 10:15:33 |
| hexa | so log compression is probably the most interesting bit | 10:15:40 |
