mirror of
https://github.com/tahoe-lafs/tahoe-lafs.git
synced 2024-12-22 22:32:23 +00:00
3f887f9279
- Use the subunitv2-file reporter to allow for nicer error handling - Undo the depgraph.sh change, see if it really matters - Rename passing -> ratchet-passing to distinguish from ported modules tracker - Misc. documentation and ratchet.sh improvements
38 lines
959 B
Bash
Executable File
38 lines
959 B
Bash
Executable File
#!/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 "../.."
|
|
|
|
# Since both of the next calls are expected to exit non-0, relax our guard.
|
|
set +e
|
|
SUBUNITREPORTER_OUTPUT_PATH="$base/results.subunit2" trial --reporter subunitv2-file allmydata
|
|
subunit2junitxml < "$base/results.subunit2" > "$base/results.xml"
|
|
set -e
|
|
|
|
# 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
|
|
git diff "$tracking_filename"
|
|
|
|
exit $code
|