nix-output-monitor
nix-output-monitor copied to clipboard
maralorn
Pipe your nix-build output through the nix-output-monitor a.k.a nom to get additional information while building.
I am using the version from current nixpkgs (`nixos-unstable` branch). I found `~/.cache/nix-output-monitor/build-reports.csv` contains a single line even a lot of packages have been built. The line is like: ```...
Assumption is that nom exits too fast to print the error the first time. 
Currently we only determine dependencies by looking into derivations: There we have inputDerivations and inputSrcs. But there is actually another kind of dependency: storePaths can reference other store paths without...
* via flags * via file * via runtime keypress
Happens when nix fails when no errors where printed.
- [ ] Use enum-type for platforms - [ ] Replace dense intmaps with arrays. (Maybe make an opaque data type with fast reverse lookup hidden away.) - [ ]...
With this derivation: ```nix { pkgs ? (import {}) }: pkgs.stdenv.mkDerivation { name = "robot-that-screams"; buildCommand = '' for _ in {0..1000000}; do echo AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA done ''; } ``` nix-build...
The memory footprint shows that a large part are the Maps in which we try to efficiently store different information. Maybe we can make this faster/smaller with a HashMap. Also...