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

t/351-deps-forget: remove a test that occasionally flakes.

Browse source 
This is unfixable when running with -j > 1 because of how the current
t/flush-cache script works.  We'll only be able to fix that after
making a more granular flush-cache tool, which is already on my todo
list.
This commit is contained in:
Avery Pennarun 2018-12-31 19:35:56 -05:00
commit 576e980c0e
1 changed files with 11 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

12
t/351-deps-forget/all.do
View file

@ -196,7 +196,17 @@ while read pre update post subran ran warn src targ ood XX; do
if [ "$ood" = 1 ]; then
is_ood || exit 35
else
! is_ood || exit 36
# FIXME: can't test this, as running ../flush-cache causes
# bork to always be out of date (since it is redo-always),
# and other parallel tests might run ../flush-cache
# at any time.
#
# We can fix this when we have a more granular flush-cache
# so that other tests can only flush their own targets, not
# ours.
#
# ! is_ood || exit 36
:
fi
# FIXME: I'd like to not depend on the specific wording of warning