about summary refs log tree commit diff
path: root/tests
AgeCommit message (Collapse)AuthorFilesLines
2004-10-27 * Bug fix in parsing of /* ... */ comments; due to longest matchEelco Dolstra3-1/+13
regexp there could be only one such comment per file.
2004-10-27 * Remove ancient Fix tests.Eelco Dolstra22-3/+145
* Add automated Nix expression language tests.
2004-08-19 * Make sure that no build hook is set by default in the tests.Eelco Dolstra2-1/+2
* Don't use `seq' - some primitive, obsolete operating systems (Darwin) don't have it.
2004-06-28 * Typo.Eelco Dolstra1-1/+1
2004-06-28 * Added a switch `--fallback'. From the manual:Eelco Dolstra4-4/+5
Whenever Nix attempts to realise a derivation for which a closure is already known, but this closure cannot be realised, fall back on normalising the derivation. The most common scenario in which this is useful is when we have registered substitutes in order to perform binary distribution from, say, a network repository. If the repository is down, the realisation of the derivation will fail. When this option is specified, Nix will build the derivation instead. Thus, binary installation falls back on a source installation. This option is not the default since it is generally not desirable for a transient failure in obtaining the substitutes to lead to a full build from source (with the related consumption of resources).
2004-06-25 * A flag `--keep-going / -k' to keep building goals if one fails, asEelco Dolstra2-5/+5
much as possible. (This is similar to GNU Make's `-k' flag.) * Refactoring to implement this: previously we just bombed out when a build failed, but now we have to clean up. In particular this means that goals must be freed quickly --- they shouldn't hang around until the worker exits. So the worker now maintains weak pointers in order not to prevent garbage collection. * Documented the `-k' and `-j' flags.
2004-06-24 * Add a test to check that when we cannot realise a closureEelco Dolstra3-3/+26
expression, we should invalidate it and go back to the derivation for which it is a successor.
2004-06-24 * Multiple and/or failing substitutes now work.Eelco Dolstra3-7/+12
2004-06-24 * A test for multiple and/or failing substitutes.Eelco Dolstra5-5/+80
2004-06-21 * Missing files added to `make dist'.Eelco Dolstra1-1/+2
2004-06-20 * Re-enable support for substitutes in the normaliser.Eelco Dolstra5-1/+61
* A better substitute mechanism. Instead of generating a store expression for each store path for which we have a substitute, we can have a single store expression that builds a generic program that is invoked to build the desired store path, which is passed as an argument. This means that operations like `nix-pull' only produce O(1) files instead of O(N) files in the store when registering N substitutes. (It consumes O(N) database storage, of course, but that's not a performance problem). * Added a test for the substitute mechanism. * `nix-store --substitute' reads the substitutes from standard input, instead of from the command line. This prevents us from running into the kernel's limit on command line length.
2004-06-19 * Re-enable build hooks.Eelco Dolstra1-3/+2
2004-06-18 * Big refactoring. Move to a much more explicitly state machine basedEelco Dolstra2-2/+5
approach. This makes it much easier to add extra complexity in the normaliser / realiser (e.g., build hooks, substitutes).
2004-05-13 * Set the executable bit.Eelco Dolstra1-0/+0
2004-05-13 * Perform all tests.Eelco Dolstra1-4/+2
2004-05-13 * The build hooks used to implement distributed builds can now be runEelco Dolstra4-10/+16
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 * Use `-j0'.Eelco Dolstra1-8/+1
2004-05-12 * A switch `-j NUMBER' to set the maximum number of parallel jobs (0 =Eelco Dolstra1-1/+1
no limit). * Add missing file to distribution.
2004-05-12 * Broken test.Eelco Dolstra1-3/+3
2004-05-12 * An quick and dirty hack to support distributed builds.Eelco Dolstra4-2/+59
2004-05-11 * True parallel builds. Nix can now run as many build jobs inEelco Dolstra4-14/+13
parallel as possible (similar to GNU Make's `-j' switch). This is useful on SMP systems, but it is especially useful for doing builds on multiple machines. The idea is that a large derivation is initiated on one master machine, which then distributes sub-derivations to any number of slave machines. This should not happen synchronously or in lock-step, so the master must be capable of dealing with multiple parallel build jobs. We now have the infrastructure to support this. TODO: substitutes are currently broken.
2004-05-04 * A test to verify that Nix executes build jobs in parallel, ifEelco Dolstra4-3/+80
possible. This test fails right now because this hasn't been implemented right now. Yes, I'm doing Test-Driven Development! ;-)
2004-05-04 * 1000th revision!Eelco Dolstra4-2/+50
* A test to verify that locking of output paths (caused by concurrent invocations of Nix) works correctly.
2004-05-04 * Another test.Eelco Dolstra6-2/+66
2004-05-04 * Grrr. TESTS are not included in EXTRA_DIST.Eelco Dolstra1-1/+1
2004-05-04 * Allow the location of the store etc. to be specified usingEelco Dolstra5-0/+64
environment variables. * Started adding some automatic tests. * Do a `make check' when building RPMs.