Staging | 382 Members | |
| Staging merges | Find currently open staging-next PRs: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+sort%3Aupdated-desc+head%3Astaging-next+head%3Astaging-next-21.05+is%3Aopen | 125 Servers |
| Sender | Message | Time |
|---|---|---|
| 11 May 2026 | ||
| groff: https://github.com/NixOS/nixpkgs/pull/517946#issuecomment-4420481095 | 13:35:17 | |
| On 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 | |
| Ouch | 13:38:14 | |
| Welp | 13:38:15 | |
| 16s to display an important man page sounded pretty bad to me. | 13:39:36 | |
| Weird. The error did not look transient, but I can't reproduce it locally, so 🤞 | 13:46:40 | |
| 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 | |
| * 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 | |
| Restarted. The big NixOS channels depend on the latest kernel. | 13:59:48 | |
| * Restarted. The big NixOS channels depend on the latest kernel IIRC. | 14:00:08 | |
| wild | 14:00:08 | |
| how often do we have out of space issues these days? | 14:00:21 | |
| I do see the tmpfs space missing sometimes. | 14:00:55 | |
| Maybe we'd better simply abandon tmpfs for the builds in the infra. | 14:01:16 | |
| I thought about backing it with additional swap for spillover | 14:01:21 | |
| so we'd get the best of both worlds | 14:01:32 | |
| (we'll not in the best channel for this topic, but it doesn't really matter) | 14:01:40 | |
| * (we're not in the best channel for this topic, but it doesn't really matter) | 14:01:46 | |
| Redacted or Malformed Event | 14:02:09 | |
| Redacted or Malformed Event | 14:02:11 | |
| Maybe, if it doesn't spill commonly. | 14:02:13 | |
| tmpfs + disk swap is less efficient than normal FS on the same drive in case it does spill. | 14:02:48 | |
| is that so? | 14:03:14 | |
| At least I think it was that way. Probably due to better work with consecutive storage of files. | 14:03:49 | |
| Well, 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 | |
| https://github.com/rust-lang/rust/issues/153879 | 14:25:51 | |
| I'm seeing a hash mismatch for yara on staging. Don't suppose anybody apart from r-ryantm got the old hash? Would like to see what's changed. | 14:49:52 | |
| aha https://github.com/NixOS/nixpkgs/pull/518630 | 14:50:27 | |
| Maybe needed to explain better, at least from what I understood. Rust removed those 2 traits around 2026-01-27 nightly version:https://github.com/rust-lang/rust/commit/0eaef592336f0c12cd9648c989f360308d842d2d chromium noticed it in their regular rollout:
which split that code into 2 cfg conditionals with rustversion::before and rustversion::since based on nightly version where those traits got removed
chromium everything is fine, nightly versions before and after work.But if you use stable toolchain with RUSTC_BOOTSTRAP afaik rustversion does not do compares between "stable" and "nightly".It just sets rustversion::before(some_date_here) as true and rustversion::since(some_date_here) as false, because comparison is implemented as PartialOrd that way:Stable | Beta < Nightly < Devhttps://github.com/dtolnay/rustversion/blob/a1dfebcd35f6082886548156f02f3832f52c0853/src/bound.rs#L51-L55 So on stable rust we always get part with these traits ( rustversion::before(2026-01-27)), unless we revert temp fix removal in https://github.com/chromium/chromium/commit/90b77efcecb262823fadb67b0ce218846cd9e756 that removes them.It worked with rust 1.94 because it still had traits, probably why backport to versions before was needed: https://github.com/NixOS/nixpkgs/blob/6443f9dfb27aa6defabd6104784332020a319af1/pkgs/applications/networking/browsers/chromium/common.nix#L614-L625 Now it is the opposite. | 15:23:10 | |
| Maybe needed to explain better, at least from what I understood. Rust removed those 2 traits around 2026-01-27 nightly version:https://github.com/rust-lang/rust/commit/0eaef592336f0c12cd9648c989f360308d842d2d chromium noticed it in their regular rollout:
cfg conditionals with rustversion::before and rustversion::since based on nightly version where those traits got removed
chromium everything is fine, nightly versions before and after work.But if you use stable toolchain with RUSTC_BOOTSTRAP afaik rustversion does not do compares between "stable" and "nightly".It just sets rustversion::before(some_date_here) as true and rustversion::since(some_date_here) as false, because comparison is implemented as PartialOrd that way:Stable | Beta < Nightly < Devhttps://github.com/dtolnay/rustversion/blob/a1dfebcd35f6082886548156f02f3832f52c0853/src/bound.rs#L51-L55 So on stable rust we always get part with these traits ( rustversion::before(2026-01-27)), unless we revert temp fix removal in https://github.com/chromium/chromium/commit/90b77efcecb262823fadb67b0ce218846cd9e756 that removes them.It worked with rust 1.94 because it still had traits, probably why backport to versions before was needed: https://github.com/NixOS/nixpkgs/blob/6443f9dfb27aa6defabd6104784332020a319af1/pkgs/applications/networking/browsers/chromium/common.nix#L614-L625 Now it is the opposite. | 15:23:51 | |