ab59f308b1
* move: legacy >> test/ * move: tests >> test/ * rename unittests * update CI * tests4pl * tests_pytorch * proxi * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci * ci * link * cli * standalone * fixing * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci * . * Apply suggestions from code review Co-authored-by: Akihiro Nitta <nitta@akihironitta.com> * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci * alone * test -> tests * Standalone fixes * ci * Update * More fixes * Fix coverage * Fix mypy * mypy * Empty-Commit * Fix * mypy just for pl * Fix standalone Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: Akihiro Nitta <nitta@akihironitta.com> Co-authored-by: Carlos Mocholí <carlossmocholi@gmail.com> |
||
|---|---|---|
| .. | ||
| checkpoints | ||
| README.md | ||
| back-compatible-versions.txt | ||
| generate_checkpoints.sh | ||
| simple_classif_training.py | ||
README.md
Maintaining back-compatibility with come legacy versions
The aim of this section is set some baselines and workflows/guidelines for maintaining back compatibility with some legacies version of PL
At this moment we focus on ability running old checkpoints, so the flow here is to create a checkpoint with every release and store it in our public AWS storage and so each CI testing will pull this archive and test loading and resuming training with this model.
If you want to pull all saved version-checkpoints for local testing/development, call
bash .actions/pull_legacy_checkpoints.sh
To back populate collection with past version you can use following bash:
bash generate_checkpoints.sh "1.3.7" "1.3.8"
zip -r checkpoints.zip checkpoints/