forks/apenwarr-redo
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Whoops, redo-oob was slightly wrong when used with -j.

Browse source 
We called 'redo' instead of 'redo-ifchange' on our indeterminate objects.
Since other instances of redo-oob might be running at the same time, this
could cause the same object to get rebuilt more than once unnecessarily.
The unit tests caught this, I just didn't notice earlier.
This commit is contained in:
Avery Pennarun 2010-12-11 05:50:29 -08:00
commit 91630a892a
3 changed files with 8 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

3
vars.py
View file

@ -25,3 +25,6 @@ while BASE and BASE.endswith('/'):
UNLOCKED = os.environ.get('REDO_UNLOCKED', '') and 1 or 0
os.environ['REDO_UNLOCKED'] = '' # not inheritable by subprocesses
NO_OOB = os.environ.get('REDO_NO_OOB', '') and 1 or 0
os.environ['REDO_NO_OOB'] = '' # not inheritable by subprocesses