From 3d38a498404bf842ca479d42d18def1f472a6fb0 Mon Sep 17 00:00:00 2001 From: Eelco Dolstra Date: Wed, 17 Nov 2010 17:32:25 +0000 Subject: * In the download size indication, take binary patches into account. Hopefully this doesn't slow things down too much. --- tests/binary-patching.sh | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'tests/binary-patching.sh') diff --git a/tests/binary-patching.sh b/tests/binary-patching.sh index 8d7788fb61..26a499727f 100644 --- a/tests/binary-patching.sh +++ b/tests/binary-patching.sh @@ -1,5 +1,7 @@ source common.sh +clearManifests + mkdir -p $TEST_ROOT/cache2 $TEST_ROOT/patches RESULT=$TEST_ROOT/result @@ -29,5 +31,9 @@ $NIX_BIN_DIR/nix-pull file://$TEST_ROOT/manifest2 # To make sure that we're using the patch, delete the full NARs. rm -f $TEST_ROOT/cache2/* +# Make sure that the download size prediction uses the patch rather +# than the full download. +$nixbuild -o $RESULT binary-patching.nix --arg version 2 --dry-run 2>&1 | grep -q "0.01 MiB" + # Now rebuild it. This should use the patch generated above. $nixbuild -o $RESULT binary-patching.nix --arg version 2 -- cgit 1.4.1