!UNVBThoJtlIiVwiDjU:nixos.org

Staging

375 Members
Staging merges | Running staging cycles: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+is%3Aopen+head%3Astaging-next+head%3Astaging-next-25.11 | Review Reports: https://malob.github.io/nix-review-tools-reports/125 Servers

Load older messages


SenderMessageTime
11 May 2026
@hexa:lossy.networkhexaor rather I clicked and it keeps loading 🤔12:35:56
@vcunat:matrix.orgVladimír ČunátMost likely because eval is in late stage, so a huge postgresql transaction hogs everything involved.12:37:12
@hexa:lossy.networkhexathat tracks12:37:46
@k900:0upti.meK900Did we merge a big rebuild into next13:28:07
@vcunat:matrix.orgVladimír Čunátgroff: https://github.com/NixOS/nixpkgs/pull/517946#issuecomment-442048109513:35:17
@vcunat:matrix.orgVladimír ČunátOn Hydra it looked like wasting around 7k jobs. (but part of that might've been due to other changes) Not that bad, considering that it's *-linux jobs.13:37:11
@k900:0upti.meK900Ouch13:38:14
@k900:0upti.meK900Welp13:38:15
@vcunat:matrix.orgVladimír Čunát16s to display an important man page sounded pretty bad to me.13:39:36
@vcunat:matrix.orgVladimír ČunátWeird. The error did not look transient, but I can't reproduce it locally, so 🤞13:46:40
@bart:bartoostveen.nlBart

Not sure if this is the right channel for this, but this build failed because of disk space: https://hydra.nixos.org/build/328832145, would be nice if this would build correctly for the next unstable bump

13:54:00
@bart:bartoostveen.nlBart *

Not sure if this is the right channel for this, but this build failed because of disk space: <https://hydra.nixos.org/build/328832145>, would be nice if this would be cached for the next unstable bump

13:54:11
@vcunat:matrix.orgVladimír ČunátRestarted. The big NixOS channels depend on the latest kernel.13:59:48
@vcunat:matrix.orgVladimír Čunát* Restarted. The big NixOS channels depend on the latest kernel IIRC.14:00:08
@hexa:lossy.networkhexawild14:00:08
@hexa:lossy.networkhexahow often do we have out of space issues these days?14:00:21
@vcunat:matrix.orgVladimír ČunátI do see the tmpfs space missing sometimes.14:00:55
@vcunat:matrix.orgVladimír ČunátMaybe we'd better simply abandon tmpfs for the builds in the infra.14:01:16
@hexa:lossy.networkhexaI thought about backing it with additional swap for spillover14:01:21
@hexa:lossy.networkhexaso we'd get the best of both worlds14:01:32
@vcunat:matrix.orgVladimír Čunát(we'll not in the best channel for this topic, but it doesn't really matter)14:01:40
@vcunat:matrix.orgVladimír Čunát* (we're not in the best channel for this topic, but it doesn't really matter)14:01:46
@hexa:lossy.networkhexaRedacted or Malformed Event14:02:09
@hexa:lossy.networkhexaRedacted or Malformed Event14:02:11
@vcunat:matrix.orgVladimír ČunátMaybe, if it doesn't spill commonly.14:02:13
@vcunat:matrix.orgVladimír Čunáttmpfs + disk swap is less efficient than normal FS on the same drive in case it does spill.14:02:48
@hexa:lossy.networkhexais that so?14:03:14
@vcunat:matrix.orgVladimír ČunátAt least I think it was that way. Probably due to better work with consecutive storage of files.14:03:49
@vcunat:matrix.orgVladimír ČunátWell, just conclusions here. I think it's unlikely to make i big difference for our use case. Killing tmpfs is just easier. I had done it on some of our machines already.14:05:14
@teutat3s:pub.solarteutat3shttps://github.com/rust-lang/rust/issues/15387914:25:51

Show newer messages


Back to Room ListRoom Version: 6