We currently have to rebase dev-* onto release-* every configuration release, in order to compare the next config update against the one just released. This is because we use the dev-* branches testing/checksum/historical-*hr-checksum.json file to compare against the newly created checksum, as that is the default --checksum-path of model-configs-test.
Now, test-repro.yml can select which branch (or config tag) we want to compare against explicitly, rather than relying on a model-configs-test default.
In this PR:
Update test-repro.yml to take in a renamed config-tag->config-ref input and a new optional compared-config-ref input, which more explicitly notes that one config-ref will be compared with another, rather than relying on the default --checksum-path of ./testing/checksum/.
Updated all workflows that refer to the updated test-repro.yml.
We currently have to rebase
dev-*
ontorelease-*
every configuration release, in order to compare the next config update against the one just released. This is because we use thedev-*
branchestesting/checksum/historical-*hr-checksum.json
file to compare against the newly created checksum, as that is the default--checksum-path
ofmodel-configs-test
.Now,
test-repro.yml
can select which branch (or config tag) we want to compare against explicitly, rather than relying on amodel-configs-test
default.In this PR:
test-repro.yml
to take in a renamedconfig-tag
->config-ref
input and a new optionalcompared-config-ref
input, which more explicitly notes that one config-ref will be compared with another, rather than relying on the default--checksum-path
of./testing/checksum/
.test-repro.yml
.${{ env.EXPERIMENT_LOCATION }}/base-experiment
and${{ env.EXPERIMENT_LOCATION }}/test-venv
separately, delete everything in${{ env.EXPERIMENT_LOCATION }}/*
. Will need @jo-basevi s opinion on this one before merging!References #33