| 30 Jan 2026 |
 Ihar Hrachyshka | swift fix: https://github.com/NixOS/nixpkgs/pull/485174 | 00:19:59 |
 Austin Horstman | nice, looks like devedition got cancelled :S | 00:55:37 |
| Ihar Hrachyshka | I have no idea what cancelled means. do you? does it indicate any issue in the package still? | 01:03:18 |
| Ihar Hrachyshka | the previous devedition timed out and looks like the nixpkgs revision included the hydra timeout: https://hydra.nixos.org/build/320734079 | 01:04:42 |
| Ihar Hrachyshka | * the previous devedition timed out and looks like the nixpkgs revision included the hydra timeout: https://hydra.nixos.org/build/320487707 | 01:05:22 |
| Ihar Hrachyshka | any idea why the timeout change seems to have no effect? | 01:05:56 |
| Ihar Hrachyshka | * any idea why the timeout change seems to have no effect? (the job duration is 3h) | 01:06:08 |
| Austin Horstman | No, I was confused by that when we were looking at logs the other day... | 01:07:44 |
| Ihar Hrachyshka | regardless, the default hydra timeout as per their own docs is 10h: https://github.com/NixOS/hydra/blob/8bc95a96f787eb36f29ceec773f5bf48bd121097/doc/manual/src/jobs.md?plain=1#L19 maybe it means something else than what I think it means :( | 01:13:30 |
| Austin Horstman | https://github.com/NixOS/hydra/issues/591 | 01:14:42 |
| Ihar Hrachyshka | there's also smth called max-silent-time that apparently can shoot a job if it doesn't print for a while | 01:18:57 |
| Austin Horstman | ah yeah | 01:19:21 |
| Austin Horstman | so might run into what i saw locally where it seemingly was hanging on the same stdout for hours | 01:19:39 |
| Ihar Hrachyshka | default at 2h though | 01:19:43 |
| Ihar Hrachyshka | yeah if it really hangs there without an output for that long... I haven't seen this happening though locally. | 01:20:19 |
| Austin Horstman | I had the one successful build the other day that took 10 hours and then each build after i had tried would just hang seemingly and i lost patience and killed them | 01:20:39 |
| Austin Horstman | always seems to be on that crash_helper | 01:21:21 |
| Ihar Hrachyshka | not always, I see some jobs end at libavcodec: https://hydra.nixos.org/build/319560478/log | 01:21:49 |
| Austin Horstman | oh okay | 01:22:01 |
| Ihar Hrachyshka | it would be nice of Hydra to 1) show if a job died because of silence and 2) include timestamps in logs. | 01:22:33 |
| Austin Horstman | i was wondering about timestamps the other day, as well | 01:23:30 |
| Austin Horstman | would be nice to see when viewing logs | 01:23:36 |
| Ihar Hrachyshka | I'm leaning to revert this LTO patch and take more time to get it to shape. maybe introduce it as a separate firefox-lto package for now not to disrupt users... | 01:24:47 |
 Randy Eckenrode | FWIW, my kosmickrisp branch is now tracking the Mesa 26.0 release candidates. | 01:30:22 |
| Ihar Hrachyshka | hm. for firefox packages, we already set meta.maxSilent = 14400; # 4h, double the default of 7200s (c.f. #129212, #129115) | 01:41:12 |
| Ihar Hrachyshka | (assuming it's respected by hydra) 4h > time the failing jobs are allowed to run | 01:43:15 |
| Ihar Hrachyshka | this comment suggests that if we would have a silence trigger we would see a message at the end informing about it https://github.com/NixOS/nixpkgs/issues/129115#issuecomment-873390598 | 01:47:18 |
| Ihar Hrachyshka | gonna run overnight this: nix build .#firefox-unwrapped 2>&1 | stdbuf -oL -eL ts '[%Y-%m-%d %H:%M:%S]' | tee build.log to see what's the longest interval between timestamps on my machine | 02:22:35 |
| Ihar Hrachyshka | * gonna run overnight this: nix build -L .#firefox-unwrapped 2>&1 | stdbuf -oL -eL ts '[%Y-%m-%d %H:%M:%S]' | tee build.log to see what's the longest interval between timestamps on my machine | 02:23:10 |
 Tristan Ross | There's a Rust project I have that I am trying to mostly statically link, it seems like it's trying to use libc++ from the system which I am believing is causing a mutex error on exit. Is there an easy way to make libc++ be statically linked instead of dynamically linked. | 11:42:17 |
