Skip to content

Commit 0432149

Browse files
committed
Merge #16921: tests: Add information on how to add Vulture suppressions
72a18a7 tests: Add information on how to add Vulture suppressions (practicalswift) Pull request description: Add information on how to add `vulture` suppressions. As requested by MarcoFalke in bitcoin/bitcoin#16906 (comment) -- your wish is my command! :) ACKs for top commit: fanquake: ACK 72a18a7 - similar sort of message as in [lint-spelling.sh](https://github.com/bitcoin/bitcoin/blob/master/test/lint/lint-spelling.sh). Tree-SHA512: b347f8cea33d4b0ba987a972979b0ac3423938084fea923a2c457a8081bc839a94ad818689d147477104b9197dc35be413f76a96026cd1507b4411d7513e3464
2 parents a73775e + 72a18a7 commit 0432149

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

test/lint/lint-python-dead-code.sh

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,11 @@ if ! command -v vulture > /dev/null; then
1313
exit 0
1414
fi
1515

16-
vulture \
16+
VULTURE_SUPPRESSIONS=$(dirname "${BASH_SOURCE[0]}")/lint-python-dead-code-whitelist
17+
if ! vulture \
1718
--min-confidence 60 \
1819
$(git rev-parse --show-toplevel) \
19-
$(dirname "${BASH_SOURCE[0]}")/lint-python-dead-code-whitelist
20+
"${VULTURE_SUPPRESSIONS}"; then
21+
echo "False positives? Suppressions can be added to ${VULTURE_SUPPRESSIONS}"
22+
exit 1
23+
fi

0 commit comments

Comments
 (0)