File tree 2 files changed +10
-5
lines changed
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
2
2
3
3
on :
4
+ workflow_dispatch :
4
5
schedule :
5
6
- cron : " 0 0 * * *" # every day at midnight
6
7
@@ -245,6 +246,8 @@ jobs:
245
246
run_flax_tpu_tests :
246
247
name : Nightly Flax TPU Tests
247
248
runs-on : docker-tpu
249
+ if : github.event_name == 'schedule'
250
+
248
251
container :
249
252
image : diffusers/diffusers-flax-tpu
250
253
options : --shm-size "16gb" --ipc host -v /mnt/hf_cache:/mnt/cache/ --privileged
@@ -355,6 +358,7 @@ jobs:
355
358
run_nightly_tests_apple_m1 :
356
359
name : Nightly PyTorch MPS tests on MacOS
357
360
runs-on : [ self-hosted, apple-m1 ]
361
+ if : github.event_name == 'schedule'
358
362
359
363
steps :
360
364
- name : Checkout diffusers
Original file line number Diff line number Diff line change 23
23
If releasing on a special branch, copy the updated README.md on the main branch for the commit you will make
24
24
for the post-release and run `make fix-copies` on the main branch as well.
25
25
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 .
27
27
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
31
29
message: "Release: <RELEASE>" and push.
32
30
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
+
33
34
5. Wait for the tests on main to be completed and be green (otherwise revert and fix bugs).
34
35
35
36
6. 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