[CI] Run periodic jobs only on pytorch/pytorch repo #138874
Conversation
Github by default tries to not run periodic jobs on forks, see https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/disabling-and-enabling-a-workflow But there is a special test repo called `pytorch/canary`, that will run those workflows for next 60 days, which is a waste of resources
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/138874
Note: Links to docs will display an error until the docs builds have been completed. ❌ 1 New FailureAs of commit 2bc6eb5 with merge base 889717a ( NEW FAILURE - The following job has failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
malfet
added
ciflow/trunk
There was a problem hiding this comment.
Nice! Could you disable those perf benchmark jobs too, i.e. https://github.com/pytorch/pytorch/blob/main/.github/workflows/inductor-perf-test-nightly-aarch64.yml?
Wow, I've never realized how many periodic jobs we have... Almost every workflow has some periodic aspect to it @ZainRizvi do we have numbers on resource utilization per github event type? |
Yeah, it takes me by surprise too, I guess we just don't pay attention to canary. I don't see a big monthly bill from canary though https://torchci-git-wdvr-costanalysis-fbopensource.vercel.app/cost_analysis?startDate=2023-10-26&endDate=2024-10-25&granularity=month&groupby=workflow_name&chartType=line&yAxis=cost, still a waste nonetheless. |
|
@pytorchbot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Merge failedReason: 1 mandatory check(s) failed. The first few are: Dig deeper by viewing the failures on hud |
|
@pytorchbot merge -f "Macs are gone" |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
4 participants
Github by default tries to not run periodic jobs on forks, see https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/disabling-and-enabling-a-workflow
But there is a special test repo called
pytorch/canary, that will run those workflows for next 60 days, which is a waste of resources