From 97dd2fab72a265ec0f4cba78450661be6f7f0fe2 Mon Sep 17 00:00:00 2001 From: Itamar Turner-Trauring Date: Fri, 14 Aug 2020 13:08:24 -0400 Subject: [PATCH] Delete. --- misc/python3/ratchet.sh | 48 ----------------------------------------- 1 file changed, 48 deletions(-) delete mode 100755 misc/python3/ratchet.sh diff --git a/misc/python3/ratchet.sh b/misc/python3/ratchet.sh deleted file mode 100755 index 72a6ac4ed..000000000 --- a/misc/python3/ratchet.sh +++ /dev/null @@ -1,48 +0,0 @@ -#!/usr/bin/env bash -set -euxo pipefail -tracking_filename="ratchet-passing" - -# Start somewhere predictable. -cd "$(dirname $0)" -base=$(pwd) - -# Actually, though, trial outputs some things that are only gitignored in the project root. -cd "../.." - -export SUBUNITREPORTER_OUTPUT_PATH="$base/results.subunit2" -# Since the next two calls are expected to exit non-0, relax our guard. -trial --reporter=subunitv2-file allmydata || true -subunit2junitxml < "${SUBUNITREPORTER_OUTPUT_PATH}" > "$base/results.xml" || true - -# Okay, now we're clear. -cd "$base" - -# Make sure ratchet.py itself is clean. -python3 -m doctest ratchet.py - -# Now see about Tahoe-LAFS (also expected to fail) ... -set +e -python3 ratchet.py up results.xml "$tracking_filename" -code=$? -set -e - -# Emit a diff of the tracking file, to aid in the situation where changes are -# not discovered until CI (where TERM might `dumb`). -if [ $TERM = 'dumb' ]; then - export TERM=ansi -fi - -echo "The ${tracking_filename} diff is:" -echo "=================================" -# "git diff" gets pretty confused in this execution context when trying to -# write to stdout. Somehow it fails with SIGTTOU. -git diff -- "${tracking_filename}" > tracking.diff -cat tracking.diff -echo "=================================" - -if [ -n "${ARTIFACTS}" ]; then - cp "${SUBUNITREPORTER_OUTPUT_PATH}" "$ARTIFACTS" -fi - -echo "Exiting with code ${code} from ratchet.py." -exit ${code}