From 824b154ce82a76bfc604b3084b18e06af4e3d007 Mon Sep 17 00:00:00 2001 From: Eelco Dolstra Date: Mon, 16 Feb 2009 09:24:20 +0000 Subject: * Release output locks as soon as possible, not when the destructor of 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. --- src/libstore/build.cc | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'src/libstore/build.cc') diff --git a/src/libstore/build.cc b/src/libstore/build.cc index d44dcf0ff0..5f1eb3415e 100644 --- a/src/libstore/build.cc +++ b/src/libstore/build.cc @@ -1023,6 +1023,8 @@ void DerivationGoal::tryToBuild() } catch (BuildError & e) { printMsg(lvlError, e.msg()); + outputLocks.unlock(); + buildUser.release(); if (printBuildTrace) { if (usingBuildHook) printMsg(lvlError, format("@ hook-failed %1% %2% %3% %4%") @@ -1130,6 +1132,8 @@ void DerivationGoal::buildDone() } catch (BuildError & e) { printMsg(lvlError, e.msg()); + outputLocks.unlock(); + buildUser.release(); if (printBuildTrace) { /* When using a build hook, the hook will return a remote build failure using exit code 100. Anything @@ -2068,6 +2072,7 @@ void DerivationGoal::computeClosure() create new lock files with the same names as the old (unlinked) lock files. */ outputLocks.setDeletion(true); + outputLocks.unlock(); } -- cgit 1.4.1