874d111d60
verify keeps its dependencies and workspace build in a cache saved by main's runs (Swatinem/rust-cache). The new parity job runs on the Mac mini's self-hosted runner (label horizon-game), which holds the maintainer's own Minecraft files: tools/ci/vanilla-data.sh links .local/ to the runner's copy and prepares the resources with the pull request's own horizon-prepare, once per preparer version; then tools/parity.py --changed <base> runs only the harnesses whose traced dependencies changed since the merge base and that have no pass for their current inputs. A fork's pull request runs it only when a maintainer adds run-parity, once per label, on the commit it had then. parity.py: --changed REF, and linux_only in tools/parity_hosts.json for harnesses that differ on other platforms for a reason that is not a Horizon bug (skipped there with the reason, unless named). docs/release-flow.md starts with the pull request checks and merging. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
17 lines
847 B
Bash
Executable File
17 lines
847 B
Bash
Executable File
#!/usr/bin/env bash
|
|
# The tools the vanilla harnesses need, on the self-hosted Mac mini runner (label horizon-game): its service
|
|
# starts with a bare PATH. Python 3.13 and the JDK pinned by research-lock.json come from the machine, never
|
|
# from a download. Writes them to $GITHUB_PATH and $GITHUB_ENV for the next steps.
|
|
set -euo pipefail
|
|
java_major=$(sed -n 's/.*"java_major": *\([0-9]*\).*/\1/p' research-lock.json | head -1)
|
|
bin="$RUNNER_TEMP/horizon-bin"
|
|
mkdir -p "$bin"
|
|
if [ "$(uname)" = Darwin ]; then
|
|
ln -sfn /opt/homebrew/bin/python3.13 "$bin/python3"
|
|
ln -sfn /opt/homebrew/bin/python3.13 "$bin/python"
|
|
java_home=$(/usr/libexec/java_home -v "$java_major")
|
|
{ echo "$bin"; echo "$java_home/bin"; echo /opt/homebrew/bin; } >> "$GITHUB_PATH"
|
|
echo "JAVA_HOME=$java_home" >> "$GITHUB_ENV"
|
|
fi
|
|
echo "HORIZON_NO_AUDIO=1" >> "$GITHUB_ENV"
|