Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2012-09-11 | Don't put results symlinks in the tests directory | Eelco Dolstra | 1 | -1/+1 | |
2011-10-10 | * Refactoring: remove unnecessary variables from the tests. | Eelco Dolstra | 1 | -1/+1 | |
2009-03-18 | * Clean up some tests (use nix-build where appropriate). | Eelco Dolstra | 1 | -5/+1 | |
2006-03-01 | * Simplification. | Eelco Dolstra | 1 | -2/+2 | |
2006-03-01 | * Make it easy to run individual tests from the command line. | Eelco Dolstra | 1 | -0/+2 | |
2005-02-09 | * Propagate the deriver of a path through the substitute mechanism. | Eelco Dolstra | 1 | -3/+3 | |
* Removed some dead code (successor stuff) from nix-push. * Updated terminology in the tests (store expr -> drv path). * Check that the deriver is set properly in the tests. | |||||
2005-01-25 | * Fix the build hook mechanism; pass the pointer graph to the hook. | Eelco Dolstra | 1 | -1/+1 | |
2004-05-13 | * The build hooks used to implement distributed builds can now be run | Eelco Dolstra | 1 | -1/+1 | |
in parallel. Hooks are more efficient: locks on output paths are only acquired when the hook says that it is willing to accept a build job. Hooks now work in two phases. First, they should first tell Nix whether they are willing to accept a job. Nix guarantuees that no two hooks will ever be in the first phase at the same time (this simplifies the implementation of hooks, since they don't have to perform locking (?)). Second, if they accept a job, they are then responsible for building it (on the remote system), and copying the result back. These can be run in parallel with other hooks and locally executed jobs. The implementation is a bit messy right now, though. * The directory `distributed' shows a (hacky) example of a hook that distributes build jobs over a set of machines listed in a configuration file. | |||||
2004-05-12 | * An quick and dirty hack to support distributed builds. | Eelco Dolstra | 1 | -0/+12 | |