saymrwulf/pytorch
1
0
Fork 0
mirror of https://github.com/saymrwulf/pytorch.git synced 2026-05-15 21:00:47 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
pytorch/.github/scripts
History
Jane Xu 655fc51f07 [GH1] Relanding #80064 to erase double messaging as it was overwritten by mistake (#80550) 
https://github.com/pytorch/pytorch/pull/77943 accidentally overwrote #80064. We can revert that PR and reland it later or we can land this fix PR as it is one line.
Pull Request resolved: https://github.com/pytorch/pytorch/pull/80550
Approved by: https://github.com/suo
2022-06-29 17:55:05 +00:00
..
build_publish_nightly_docker.sh ci: Fix cudatoolkit issue, make docker builds testable 2022-03-09 19:49:05 +00:00
convert_lintrunner_annotations_to_github.py [ci] use lintrunner in CI 2022-04-15 00:08:21 +00:00
ensure_actions_will_cancel.py Workflow consolidation for GitHub actions 2022-03-21 14:15:03 +00:00
export_pytorch_labels.py
generate_binary_build_matrix.py Upgrade CI to ROCm 5.1 2022-04-28 00:02:07 +00:00
generate_ci_workflows.py [ci] remove ciflow/all (#78317) 2022-05-26 16:25:25 +00:00
generate_pytorch_version.py
get_workflow_job_id.py [ci] Fix bug in get_workflow_job_id.py 2022-04-08 21:09:38 +00:00
gitutils.py [GHF] Retry push unconditionally (#77426) 2022-05-13 17:09:01 +00:00
gql_mocks.json [mergebot] add additional checks (#79317) 2022-06-13 19:28:29 +00:00
install_nvidia_utils_linux.sh Cuda 11.6 Disable failing tests (#75420) 2022-04-07 22:43:15 +00:00
kill_active_ssh_sessions.ps1
lint_native_functions.py [lint] upgrade mypy to latest version 2022-05-03 20:51:34 +00:00
parse_ref.py
print_latest_commits.py [ci] fix viable/strict promotion (#80399) 2022-06-28 01:03:53 +00:00
process_commit.py Fix alignment, make sure release labels are included (#73739) 2022-03-03 16:30:55 +00:00
README.md [BE] add readme for .github, located in .github/scripts 2022-04-01 19:53:44 +00:00
report_git_status.sh
run_torchbench.py Add userbenchmark support to TorchBench CI (#78794) 2022-06-03 21:07:36 +00:00
test_gitutils.py Add gitutils tests (#71580) 2022-01-20 14:33:41 -08:00
test_print_latest_commits.py [ci] fix viable/strict promotion (#80399) 2022-06-28 01:03:53 +00:00
test_trymerge.py [mergebot] Create land time check options (#77943) 2022-06-27 22:28:12 +00:00
test_tryrebase.py rebase via comment - rebase to any branch (#78772) 2022-06-03 17:13:11 +00:00
trymerge.py [GH1] Relanding #80064 to erase double messaging as it was overwritten by mistake (#80550) 2022-06-29 17:55:05 +00:00
tryrebase.py [GHF][BE] Comment on reverted commit (#79913) 2022-06-22 02:46:48 +00:00
update_commit_hashes.py automate hash updates - add new lint to appease lint (#79832) 2022-06-20 15:56:38 +00:00
wait_for_ssh_to_drain.ps1
wait_for_ssh_to_drain.sh

README.md

pytorch/.github

NOTE: This README contains information for the .github directory but cannot be located there because it will overwrite the repo README.

This directory contains workflows and scripts to support our CI infrastructure that runs on Github Actions.

Workflows

  • Pull CI (pull.yml) is run on PRs and on master.
  • Trunk CI (trunk.yml) is run on trunk to validate incoming commits. Trunk jobs are usually more expensive to run so we do not run them on PRs unless specified.
  • Scheduled CI (periodic.yml) is a subset of trunk CI that is run every few hours on master.
  • Binary CI is run to package binaries for distribution for all platforms.

Templates

Templates written in Jinja are located in the .github/templates directory and used to generate workflow files for binary jobs found in the .github/workflows/ directory. These are also a couple of utility templates used to discern common utilities that can be used amongst different templates.

(Re)Generating workflow files

You will need jinja2 in order to regenerate the workflow files which can be installed using:

pip install -r .github/requirements.txt

Workflows can be generated / regenerated using the following command:

.github/regenerate.sh

Adding a new generated binary workflow

New generated binary workflows can be added in the .github/scripts/generate_ci_workflows.py script. You can reference examples from that script in order to add the workflow to the stream that is relevant to what you particularly care about.

Different parameters can be used to acheive different goals, i.e. running jobs on a cron, running only on trunk, etc.

ciflow (trunk)

The label ciflow/trunk can be used to run trunk only workflows. This is especially useful if trying to re-land a PR that was reverted for failing a non-default workflow.

Infra

Currently most of our self hosted runners are hosted on AWS, for a comprehensive list of available runner types you can reference .github/scale-config.yml.

Exceptions to AWS for self hosted:

  • ROCM runners

Adding new runner types

New runner types can be added by committing changes to .github/scale-config.yml. Example: https://github.com/pytorch/pytorch/pull/70474

NOTE: New runner types can only be used once the changes to .github/scale-config.yml have made their way into the default branch