nordic-dev.net/nix
nordic-dev.net/nix
2
0
Fork 0
mirror of https://github.com/NixOS/nix.git synced 2024-11-22 14:52:55 +00:00
Code Issues Packages Projects Releases Wiki Activity
2.23-maintenance
nix/tests/functional/gc-concurrent.sh

62 lines
1.5 KiB
Bash
Raw Permalink Normal View History

Ensure all functional scripts are (a) executable (b) have shebang This is good for shebang, and also good for future build system simplifications
2024-05-28 16:43:04 +00:00
#!/usr/bin/env bash
* Make it easy to run individual tests from the command line.
2006-03-01 12:15:33 +00:00
source common.sh
* Argh, stupid timing sensitive tests...
2009-03-27 22:40:22 +00:00
clearStore
* Increase the sleep periods a bit to make the test less likely to fail on slow machines. Of course it would be better if this test wasn't timing dependent...
2008-08-14 09:26:30 +00:00
Make the gc-concurrent test more reliable Use a fifo pipe to handle the synchronisation between the different threads rather than relying on delays
2020-07-02 13:43:35 +00:00
lockFifo1=$TEST_ROOT/test1.fifo
mkfifo "$lockFifo1"
drvPath1=$(nix-instantiate gc-concurrent.nix -A test1 --argstr lockFifo "$lockFifo1")
* Refactoring: remove unnecessary variables from the tests.
2011-10-10 21:32:34 +00:00
outPath1=$(nix-store -q $drvPath1)
* Add a test for a more subtle race: a process starting after the temporary root files have been read but creating outputs before the store directory has been read.
2005-01-31 22:01:55 +00:00
* Refactoring: remove unnecessary variables from the tests.
2011-10-10 21:32:34 +00:00
drvPath2=$(nix-instantiate gc-concurrent.nix -A test2)
outPath2=$(nix-store -q $drvPath2)
* Add a test to check whether concurrent garbage collection (i.e., running the collector while builds are in progress) works correctly. The test currently fails.
2005-01-28 20:36:46 +00:00
* Refactoring: remove unnecessary variables from the tests.
2011-10-10 21:32:34 +00:00
drvPath3=$(nix-instantiate simple.nix)
outPath3=$(nix-store -r $drvPath3)
* Simplify deleting .lock files in /nix/store: just don't delete them if they belong a path that's currently being built. This gets rid of some Cygwin-specific code.
2008-12-12 17:03:18 +00:00
Fix tests So all these years I was totally deluded about the meaning of "set -e". You might think that it causes statements like "false && true" or "! true" to fail, but it doesn't...
2014-08-21 19:50:19 +00:00
(! test -e $outPath3.lock)
* Simplify deleting .lock files in /nix/store: just don't delete them if they belong a path that's currently being built. This gets rid of some Cygwin-specific code.
2008-12-12 17:03:18 +00:00
touch $outPath3.lock
rm -f "$NIX_STATE_DIR"/gcroots/foo*
* Add a test for nix-log2xml.
2006-03-01 13:25:08 +00:00
ln -s $drvPath2 "$NIX_STATE_DIR"/gcroots/foo
* Simplify deleting .lock files in /nix/store: just don't delete them if they belong a path that's currently being built. This gets rid of some Cygwin-specific code.
2008-12-12 17:03:18 +00:00
ln -s $outPath3 "$NIX_STATE_DIR"/gcroots/foo2
* Acquire a global GC lock to prevent new temporary root files from being created after the garbage collector has read the temproots directory. This blocks the creation of new processes, but the garbage collector could periodically release the GC lock to allow them to run.
2005-01-31 22:23:49 +00:00
* Add a test for a more subtle race: a process starting after the temporary root files have been read but creating outputs before the store directory has been read.
2005-01-31 22:01:55 +00:00
# Start build #1 in the background. It starts immediately.
* Refactoring: remove unnecessary variables from the tests.
2011-10-10 21:32:34 +00:00
nix-store -rvv "$drvPath1" &
* Add a test for a more subtle race: a process starting after the temporary root files have been read but creating outputs before the store directory has been read.
2005-01-31 22:01:55 +00:00
pid1=$!
* Add a test to check whether concurrent garbage collection (i.e., running the collector while builds are in progress) works correctly. The test currently fails.
2005-01-28 20:36:46 +00:00
Make the gc-concurrent test more reliable Use a fifo pipe to handle the synchronisation between the different threads rather than relying on delays
2020-07-02 13:43:35 +00:00
# Wait for the build of $drvPath1 to start
cat $lockFifo1
* Add a test to check whether concurrent garbage collection (i.e., running the collector while builds are in progress) works correctly. The test currently fails.
2005-01-28 20:36:46 +00:00
* Increase the sleep periods a bit to make the test less likely to fail on slow machines. Of course it would be better if this test wasn't timing dependent...
2008-08-14 09:26:30 +00:00
# Run the garbage collector while the build is running.
* Refactoring: remove unnecessary variables from the tests.
2011-10-10 21:32:34 +00:00
nix-collect-garbage
* Add a test for a more subtle race: a process starting after the temporary root files have been read but creating outputs before the store directory has been read.
2005-01-31 22:01:55 +00:00
Make the gc-concurrent test more reliable Use a fifo pipe to handle the synchronisation between the different threads rather than relying on delays
2020-07-02 13:43:35 +00:00
# Unlock the build of $drvPath1
echo "" > $lockFifo1
* Add a test for a more subtle race: a process starting after the temporary root files have been read but creating outputs before the store directory has been read.
2005-01-31 22:01:55 +00:00
echo waiting for pid $pid1 to finish...
wait $pid1
* Add a test to check whether concurrent garbage collection (i.e., running the collector while builds are in progress) works correctly. The test currently fails.
2005-01-28 20:36:46 +00:00
* Add a test for a more subtle race: a process starting after the temporary root files have been read but creating outputs before the store directory has been read.
2005-01-31 22:01:55 +00:00
# Check that the root of build #1 and its dependencies haven't been
* Increase the sleep periods a bit to make the test less likely to fail on slow machines. Of course it would be better if this test wasn't timing dependent...
2008-08-14 09:26:30 +00:00
# deleted. The should not be deleted by the GC because they were
# being built during the GC.
* Add a test for a more subtle race: a process starting after the temporary root files have been read but creating outputs before the store directory has been read.
2005-01-31 22:01:55 +00:00
cat $outPath1/foobar
cat $outPath1/input-2/bar
* Add a test to check whether concurrent garbage collection (i.e., running the collector while builds are in progress) works correctly. The test currently fails.
2005-01-28 20:36:46 +00:00
Make the gc-concurrent test more reliable Use a fifo pipe to handle the synchronisation between the different threads rather than relying on delays
2020-07-02 13:43:35 +00:00
# Check that the build build $drvPath2 succeeds.
# It should succeed because the derivation is a GC root.
nix-store -rvv "$drvPath2"
* Add a test for a more subtle race: a process starting after the temporary root files have been read but creating outputs before the store directory has been read.
2005-01-31 22:01:55 +00:00
cat $outPath2/foobar
* Add a test for nix-log2xml.
2006-03-01 13:25:08 +00:00
* Simplify deleting .lock files in /nix/store: just don't delete them if they belong a path that's currently being built. This gets rid of some Cygwin-specific code.
2008-12-12 17:03:18 +00:00
rm -f "$NIX_STATE_DIR"/gcroots/foo*
# The collector should have deleted lock files for paths that have
# been built previously.
Fix tests So all these years I was totally deluded about the meaning of "set -e". You might think that it causes statements like "false && true" or "! true" to fail, but it doesn't...
2014-08-21 19:50:19 +00:00
(! test -e $outPath3.lock)
* Simplify deleting .lock files in /nix/store: just don't delete them if they belong a path that's currently being built. This gets rid of some Cygwin-specific code.
2008-12-12 17:03:18 +00:00
# If we run the collector now, it should delete outPath1/2.
* Refactoring: remove unnecessary variables from the tests.
2011-10-10 21:32:34 +00:00
nix-collect-garbage
Fix tests So all these years I was totally deluded about the meaning of "set -e". You might think that it causes statements like "false && true" or "! true" to fail, but it doesn't...
2014-08-21 19:50:19 +00:00
(! test -e $outPath1)
(! test -e $outPath2)
Reference in New Issue Copy Permalink