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...
		
			
				
	
	
		
			24 lines
		
	
	
	
		
			623 B
		
	
	
	
		
			Bash
		
	
	
	
	
	
			
		
		
	
	
			24 lines
		
	
	
	
		
			623 B
		
	
	
	
		
			Bash
		
	
	
	
	
	
| source common.sh
 | |
| 
 | |
| clearStore
 | |
| 
 | |
| # Produce an escaped log file.
 | |
| path=$(nix-build --log-type escapes -vv dependencies.nix --no-out-link 2> $TEST_ROOT/log.esc)
 | |
| 
 | |
| # Convert it to an XML representation.
 | |
| nix-log2xml < $TEST_ROOT/log.esc > $TEST_ROOT/log.xml
 | |
| 
 | |
| # Is this well-formed XML?
 | |
| if test "$xmllint" != "false"; then
 | |
|     $xmllint --noout $TEST_ROOT/log.xml || fail "malformed XML"
 | |
| fi
 | |
| 
 | |
| # Test nix-store -l.
 | |
| [ "$(nix-store -l $path)" = FOO ]
 | |
| 
 | |
| # Test compressed logs.
 | |
| clearStore
 | |
| rm -rf $NIX_LOG_DIR
 | |
| (! nix-store -l $path)
 | |
| nix-build dependencies.nix --no-out-link --option build-compress-log true
 | |
| [ "$(nix-store -l $path)" = FOO ]
 |