1name: unstable-periodic 2 3on: 4 schedule: 5 - cron: 45 0,4,8,12,16,20 * * * 6 - cron: 29 8 * * * # about 1:29am PDT, for mem leak check and rerun disabled tests 7 push: 8 tags: 9 - ciflow/unstable/* 10 workflow_dispatch: 11 12concurrency: 13 group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref_name }}-${{ github.ref_type == 'branch' && github.sha }}-${{ github.event_name == 'workflow_dispatch' }}-${{ github.event_name == 'schedule' }}-${{ github.event.schedule }} 14 cancel-in-progress: true 15 16permissions: read-all 17 18jobs: 19 # There must be at least one job here to satisfy GitHub action workflow syntax 20 introduction: 21 if: github.repository_owner == 'pytorch' 22 runs-on: ubuntu-latest 23 continue-on-error: true 24 steps: 25 - name: Introduce PyTorch unstable (periodic) workflow 26 run: | 27 echo "PyTorch unstable workflow is used to host experimental or flaky jobs" 28 echo " that needs to be run periodically, but doesn't impact trunk as part" 29 echo " of the stable periodic workflows." 30 echo 31 echo "In addition, a new label called ciflow/unstable can be attached to the" 32 echo " PR to trigger this workflow. That can be done either manually or" 33 echo " automatically using PyTorch auto-label bot." 34 echo 35 echo "Once the jobs are deemed stable enough (% red signal < 5% and TTS < 3h)," 36 echo " they can graduate and move back to periodic." 37