t/351-deps-forget: remove a test that occasionally flakes.
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:
parent
87bac287b6
commit
576e980c0e
1 changed files with 11 additions and 1 deletions
|
|
@ -196,7 +196,17 @@ while read pre update post subran ran warn src targ ood XX; do
|
||||||
if [ "$ood" = 1 ]; then
|
if [ "$ood" = 1 ]; then
|
||||||
is_ood || exit 35
|
is_ood || exit 35
|
||||||
else
|
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
|
fi
|
||||||
|
|
||||||
# FIXME: I'd like to not depend on the specific wording of warning
|
# FIXME: I'd like to not depend on the specific wording of warning
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue