While chutney currently runs tor's chutney test in its own CI,
it's difficult to guarantee the two won't accidentally diverge.
Probably best to use a fixed version here so that we can control
chutney version bumps and avoid surprise breakage in tor's CI.
This will also free us to intentionally make breaking changes in
chutney (though I don't have any immediate plans for any).
# TODO: This next line should not be debian-only.
- |
if [ "$CHUTNEY" = yes ]; then
- git clone --depth 1 https://gitlab.torproject.org/tpo/core/chutney.git
+ # Use a fixed version of chutney to avoid surprise breakage.
+ CHUTNEY_SHALLOW_SINCE=2024-10-28
+ CHUTNEY_COMMIT=be881a1e7c4bc8038fa13fde4a7b24e5c56349c4
+
+ git clone --shallow-since "$CHUTNEY_SHALLOW_SINCE" https://gitlab.torproject.org/tpo/core/chutney.git
+ git -C ./chutney checkout "$CHUTNEY_COMMIT"
export CHUTNEY_PATH="$(pwd)/chutney"
# Have pip install chutney's python dependencies by installing chutney
# itself.
--- /dev/null
+ o Minor feature (testing, CI):
+ - Use a fixed version of chutney (be881a1e) instead of its current HEAD.
+ This version should also be preferred when testing locally.