> OTOH, I'm mostly worried about race conditions that don't cause the build to > fail but produce a different result, and that's probably very rare. So > turning on "-j" globally might be acceptable, but some empirical results > would be needed :-) So how can they be collected? Calculate hash of output directory as well and send them to a remote database hosted on nixos so that you can get a waring:
Several other people have build the same package with exactly the same buildinputs but got a different result: your hash: yyyy hashes of other nix users xxx ,xxx ,xxx This would be fine to find other impurities as well. Don't know if we want to fix them (assembler generation depending on compiling cpu etc) But it would generate some data to look at. Of course this option must be optional Marc Weber _______________________________________________ nix-dev mailing list [email protected] https://mail.cs.uu.nl/mailman/listinfo/nix-dev
