File tree Expand file tree Collapse file tree 2 files changed +10
-5
lines changed
Expand file tree Collapse file tree 2 files changed +10
-5
lines changed Original file line number Diff line number Diff line change 1- name : Nightly tests on main
1+ name : Nightly and release tests on main/release branch
22
33on :
4+ workflow_dispatch :
45 schedule :
56 - cron : " 0 0 * * *" # every day at midnight
67
@@ -245,6 +246,8 @@ jobs:
245246 run_flax_tpu_tests :
246247 name : Nightly Flax TPU Tests
247248 runs-on : docker-tpu
249+ if : github.event_name == 'schedule'
250+
248251 container :
249252 image : diffusers/diffusers-flax-tpu
250253 options : --shm-size "16gb" --ipc host -v /mnt/hf_cache:/mnt/cache/ --privileged
@@ -355,6 +358,7 @@ jobs:
355358 run_nightly_tests_apple_m1 :
356359 name : Nightly PyTorch MPS tests on MacOS
357360 runs-on : [ self-hosted, apple-m1 ]
361+ if : github.event_name == 'schedule'
358362
359363 steps :
360364 - name : Checkout diffusers
Original file line number Diff line number Diff line change 2323 If releasing on a special branch, copy the updated README.md on the main branch for the commit you will make
2424 for the post-release and run `make fix-copies` on the main branch as well.
2525
26- 2. Run Tests for Amazon Sagemaker. The documentation is located in `./tests/sagemaker/README.md`, otherwise @philschmid .
26+ 2. Unpin specific versions from setup.py that use a git install .
2727
28- 3. Unpin specific versions from setup.py that use a git install.
29-
30- 4. Checkout the release branch (v<RELEASE>-release, for example v4.19-release), and commit these changes with the
28+ 3. Checkout the release branch (v<RELEASE>-release, for example v4.19-release), and commit these changes with the
3129 message: "Release: <RELEASE>" and push.
3230
31+ 4. Manually trigger the "Nightly and release tests on main/release branch" workflow from the release branch. Wait for
32+ the tests to complete. We can safely ignore the known test failures.
33+
33345. Wait for the tests on main to be completed and be green (otherwise revert and fix bugs).
3435
35366. Add a tag in git to mark the release: "git tag v<RELEASE> -m 'Adds tag v<RELEASE> for PyPI'"
You can’t perform that action at this time.
0 commit comments