#failures
3 discoveries · Hand-picked discoveries from the open web, newest first.
-
Zero Hydra Failures towards 26.11 NixOS release
PSA: NixOS-26.11 is about to be released by the end of November . Release process is in ZHF phase now where no major changes are allowed in master and most known failures are being fixed now. ZHF issue has a nice step-by-step on how to find and fix a broken package. I’ll not provide complete session compared to past example and will link a few ZHF fixes for this cycle here: h5v sapling fedistar fceux All fixes are one-liners. It’s a good time to contribute to nixpkgs if you never did and are thinking of it. Have fun!
trofi - All posts · EN
-
Catch Electronics Shock and Drop Failures Before Hardware Is Built
Learn how guided virtual shock and drop analysis helps engineering teams identify reliability risks before physical testing, reduce qualification iterations, optimize packaging designs, and accelerate electronics product development. What you will learn about: Why shock failures found during physical qualification are costly, and how coupled electrical, mechanical, thermal, and packaging effects make them hard to predict. How physical drop testing and traditional simulation each leave gaps in timing, expertise, setup effort, and diagnostic detail. How guided, template-based virtual workflows m
IEEE Spectrum · EN
-
Zero Hydra Failures towards 26.05 NixOS release
NixOS-26.05 is around the corner! The schedule says it should happen around 25 May. Today the release process entered ZHF phase. There most packages with build failures are expected to be addresses by the release date. https://github.com/NixOS/nixpkgs/issues/516381 contains detailed step-by-step to identify interesting packages. This time nixpkgs is full of build failures related to gcc-15 changes ( -std=gnu23 switch). An example package fix I usually try to fix at least one package during ZHF . Let’s do it again. I picked ior package. hydra says it is broken since January 2026. Most recent ht
trofi - All posts · EN