forks/apenwarr-redo
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
apenwarr-redo/t/s60-stamp
History
Avery Pennarun aa423a723f t/660-stamp: don't run at the same time as other tests in redo -j. 
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.
2018-10-12 05:20:27 -04:00
..
.gitignore t/660-stamp: don't run at the same time as other tests in redo -j. 2018-10-12 05:20:27 -04:00
a.do t/660-stamp: don't run at the same time as other tests in redo -j. 2018-10-12 05:20:27 -04:00
ab.do t/660-stamp: don't run at the same time as other tests in redo -j. 2018-10-12 05:20:27 -04:00
abc.do t/660-stamp: don't run at the same time as other tests in redo -j. 2018-10-12 05:20:27 -04:00
all.do t/660-stamp: don't run at the same time as other tests in redo -j. 2018-10-12 05:20:27 -04:00
b.do t/660-stamp: don't run at the same time as other tests in redo -j. 2018-10-12 05:20:27 -04:00
bob.do t/660-stamp: don't run at the same time as other tests in redo -j. 2018-10-12 05:20:27 -04:00
c t/660-stamp: don't run at the same time as other tests in redo -j. 2018-10-12 05:20:27 -04:00
clean.do t/660-stamp: don't run at the same time as other tests in redo -j. 2018-10-12 05:20:27 -04:00
stamptest.do t/660-stamp: don't run at the same time as other tests in redo -j. 2018-10-12 05:20:27 -04:00
stampy.do t/660-stamp: don't run at the same time as other tests in redo -j. 2018-10-12 05:20:27 -04:00
usestamp.do t/660-stamp: don't run at the same time as other tests in redo -j. 2018-10-12 05:20:27 -04:00
usestamp2.do t/660-stamp: don't run at the same time as other tests in redo -j. 2018-10-12 05:20:27 -04:00