Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2009-03-28 | * Scan for references and compute the SHA-256 hash of the output in | Eelco Dolstra | 3 | -89/+50 | |
one pass. This halves the amount of I/O. | |||||
2009-03-28 | * Don't use the non-standard __gnu_cxx::stdio_filebuf class. | Eelco Dolstra | 2 | -33/+17 | |
2009-03-28 | * Simplify communication with the hook a bit (don't use file | Eelco Dolstra | 6 | -117/+68 | |
descriptors 3/4, just use stdin/stderr). | |||||
2009-03-28 | * Clean up the output a bit. | Eelco Dolstra | 1 | -5/+5 | |
2009-03-28 | * The `fixedOutput' variable didn't get initialised when using a build | Eelco Dolstra | 1 | -5/+6 | |
hook, causing negative caching to fail randomly. | |||||
2009-03-27 | * Argh, stupid timing sensitive tests... | Eelco Dolstra | 1 | -4/+4 | |
2009-03-27 | * Debian 5.0, Ubuntu 8.10 builds. | Eelco Dolstra | 1 | -4/+8 | |
2009-03-27 | * Create /nix/store if it doesn't exist. | Eelco Dolstra | 1 | -0/+2 | |
2009-03-26 | * A job for creating a fully statically linked binary tarball. | Eelco Dolstra | 1 | -1/+22 | |
2009-03-26 | * Support doing a fully static build. Statically linked Nix binaries | Eelco Dolstra | 1 | -11/+24 | |
will be useful as a fallback on platforms for which there are no RPMs/Debs available. | |||||
2009-03-26 | * Don't use ULLONG_MAX in maxFreed - use 0 to mean "no limit". | Eelco Dolstra | 4 | -10/+8 | |
18446744073709551615ULL breaks on GCC 3.3.6 (`integer constant is too large for "long" type'). | |||||
2009-03-25 | * Negative caching, i.e. caching of build failures. Disabled by | Eelco Dolstra | 7 | -7/+140 | |
default. This is mostly useful for Hydra. | |||||
2009-03-25 | * Removed the locking.sh test; it's redundant because of the extended | Eelco Dolstra | 5 | -45/+11 | |
parallel.sh test. Also, don't call multiple nix-builds in parallel, since they can race creating .nix-build-tmp-derivation. | |||||
2009-03-25 | * Use bash in the tests. | Eelco Dolstra | 2 | -1/+2 | |
2009-03-24 | * Doh. | Eelco Dolstra | 1 | -1/+1 | |
2009-03-24 | (no commit message) | Eelco Dolstra | 1 | -1/+1 | |
2009-03-23 | * Make this test a bit more robust. It's still timing dependent | Eelco Dolstra | 3 | -10/+14 | |
though. | |||||
2009-03-23 | * Shut up a GCC warning. | Eelco Dolstra | 1 | -2/+2 | |
2009-03-23 | * No longer block while waiting for a lock on a store path. Instead | Eelco Dolstra | 5 | -28/+85 | |
poll for it (i.e. if we can't acquire the lock, then let the main select() loop wait for at most a few seconds and then try again). This improves parallelism: if two nix-store processes are both trying to build a path at the same time, the second one shouldn't block; it should first see if it can build other goals. Also, it prevents the deadlocks that have been occuring in Hydra lately, where a process waits for a lock held by another process that's waiting for a lock held by the first. The downside is that polling isn't really elegant, but POSIX doesn't provide a way to wait for locks in a select() loop. The only solution would be to spawn a thread for each lock to do a blocking fcntl() and then signal the main thread, but that would require pthreads. | |||||
2009-03-22 | * Refactoring. | Eelco Dolstra | 1 | -136/+85 | |
2009-03-22 | * Test case (currently fails): multiple Nix builds shouldn't block | Eelco Dolstra | 1 | -2/+34 | |
waiting on the same lock when there are other builds that can be done. | |||||
2009-03-22 | * Better error message when nix-store --import is applied to garbage | Eelco Dolstra | 1 | -1/+1 | |
(previously it would likely say "implementation cannot deal with > 32-bit integers"). | |||||
2009-03-22 | * NAR archives: handle files larger than 2^32 bytes. Previously it | Eelco Dolstra | 7 | -17/+48 | |
would just silently store only (fileSize % 2^32) bytes. * Use posix_fallocate if available when unpacking archives. * Provide a better error message when trying to unpack something that isn't a NAR archive. | |||||
2009-03-19 | * Future proofing: assume we can read manifests up to version 10 | Eelco Dolstra | 1 | -1/+6 | |
(which should therefore be backwards compatible). | |||||
2009-03-19 | * Disregard the Hash field in manifests. | Eelco Dolstra | 1 | -22/+5 | |
2009-03-18 | * Unify exportReferencesGraph and exportBuildReferencesGraph, and make | Eelco Dolstra | 4 | -67/+40 | |
sure that it works as expected when you pass it a derivation. That is, we have to make sure that all build-time dependencies are built, and that they are all in the input closure (otherwise remote builds might fail, for example). This is ensured at instantiation time by adding all derivations and their sources to inputDrvs and inputSrcs. | |||||
2009-03-18 | * Improve the test. | Eelco Dolstra | 1 | -2/+6 | |
2009-03-18 | * Better cleanup after tests. | Eelco Dolstra | 1 | -5/+8 | |
2009-03-18 | * Missing file. | Eelco Dolstra | 1 | -0/+1 | |
2009-03-18 | * Acquire the locks on the output paths before trying to run the build | Eelco Dolstra | 4 | -150/+78 | |
hook. This fixes a problem with log files being partially or completely filled with 0's because another nix-store process truncates the log file. It should also be more efficient. | |||||
2009-03-18 | * Clean up some tests (use nix-build where appropriate). | Eelco Dolstra | 7 | -34/+25 | |
2009-03-17 | * Regression test for exportBuildReferencesGraph. It currently fails. | Eelco Dolstra | 3 | -6/+34 | |
2009-03-17 | * Refactoring: renamed *.nix.in to *.nix. | Eelco Dolstra | 22 | -264/+209 | |
2009-03-17 | * Regression test for the `exportReferencesGraph' | Eelco Dolstra | 8 | -33/+69 | |
derivation attribute. | |||||
2009-03-17 | * Cleanup. | Eelco Dolstra | 1 | -22/+9 | |
2009-03-09 | * Make the version available to release.nix. | Eelco Dolstra | 3 | -41/+15 | |
2009-03-06 | (no commit message) | Eelco Dolstra | 1 | -1/+1 | |
2009-03-06 | (no commit message) | Eelco Dolstra | 1 | -1/+1 | |
2009-03-05 | * Install some headers in the right location. | Eelco Dolstra | 2 | -2/+6 | |
2009-03-03 | * Allow the channel to declare a name for itself. | Eelco Dolstra | 1 | -0/+6 | |
2009-02-27 | * nix-install-package: don't pollute /nix/var/nix/manifests. | Eelco Dolstra | 3 | -11/+11 | |
2009-02-27 | * Use the regular progress bar; the hash bar isn't very useful when | Eelco Dolstra | 1 | -1/+1 | |
the size of the download isn't known in advance. | |||||
2009-02-27 | * nix-build: support --option. | Eelco Dolstra | 1 | -0/+7 | |
2009-02-27 | * Allow options from the Nix config file to be overriden from the | Eelco Dolstra | 3 | -0/+21 | |
command line (e.g. "--option build-use-chroot true"). | |||||
2009-02-27 | * nix-channel: use nix-build. | Eelco Dolstra | 1 | -8/+6 | |
2009-02-27 | * Check the manifest version. | Eelco Dolstra | 1 | -3/+4 | |
2009-02-26 | * Handle base-16 hashes in manifests. | Eelco Dolstra | 1 | -1/+12 | |
2009-02-19 | * download-using-manifests: don't check the cryptographic hash of | Eelco Dolstra | 1 | -18/+30 | |
downloaded files; rather, check the hash of the unpacked store path. When the server produces bzipped NAR archives on demand (like Hydra does), the hash of the file is not known in advance; it's streamed from the server. Thus the manifest doesn't contain a hash for the bzipped NAR archive. However, the server does know the hash of the *uncompressed* NAR archive (the "NarHash" field), since it's stored in the Nix database (nix-store -q --hash /nix/store/bla). So we use that instead for checking the integrity of the download. | |||||
2009-02-19 | Replace wrong (w.r.t. PATH) sed call with in-shell substitution | Michael Raskin | 1 | -1/+2 | |
2009-02-16 | * Release output locks as soon as possible, not when the destructor of | Eelco Dolstra | 3 | -0/+14 | |
the DerivationGoal runs. Otherwise, if a goal is a top-level goal, then the lock won't be released until nix-store finishes. With --keep-going and lots of top-level goals, it's possible to run out of file descriptors (this happened sometimes in the build farm for Nixpkgs). Also, for failed derivation, it won't be possible to build it again until the lock is released. * Idem for locks on build users: these weren't released in a timely manner for failed top-level derivation goals. So if there were more than (say) 10 such failed builds, you would get an error about having run out of build users. |