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

t/660-stamp: don't run at the same time as other tests in redo -j.

Browse source 
flush-cache can cause files affected by redo-stamp to get rebuilt
unnecessarily, which the test is specifically trying to validate.
Since other tests run flush-cache at random times when using -j, this
would cause random test failures.
This commit is contained in:
Avery Pennarun 2018-10-12 04:39:09 -04:00
commit aa423a723f
14 changed files with 17 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

12
t/s60-stamp/.gitignore vendored Normal file
View file

@ -0,0 +1,12 @@
/*.log
/usestamp
/stampy
/inp
/bob
/usestamp2
/a
/b
/ab
/doing_ab
/abc
/doing_abc