pytorch/tools
Rong Rong d33066ab3f adding a build_start_time_epoch to build meta info (#61322)
Summary:
Adding a `build_start_time_epoch` as a normal field in scribe reporting.
This should fix https://github.com/pytorch/pytorch/issues/60591.

The decision was made because:
- we would like only one build (test CI job) start time as partition key string
  - the alternative is to report the duration on each test case individually which would result in duplicate numeric value upload.
- we would be easily calculate the wall-time of a test job from `MAX('time') - build_start_time_epoch` for all reporting messages with the same normal keys.

Pull Request resolved: https://github.com/pytorch/pytorch/pull/61322

Test Plan:
CI should report the extra normal field.

See: https://fburl.com/scuba/pytorch_test_times/pm6chz9w

Reviewed By: driazati

Differential Revision: D29589020

Pulled By: walterddr

fbshipit-source-id: 309fc3b01cbce76cd62f8ccd2eb0ecad27782b88
2021-07-07 16:27:13 -07:00
..
amd_build Strictly type everything in .github and tools (#59117) 2021-06-07 14:49:36 -07:00
autograd Support __rand__, __ror__ and __rxor__ (#59240) 2021-07-07 13:34:14 -07:00
clang_format_hash
code_analyzer [pytorch] fix tools/code_analyzer for llvm 11 (#60322) 2021-06-20 00:39:11 -07:00
code_coverage Strictly type everything in .github and tools (#59117) 2021-06-07 14:49:36 -07:00
codegen Add an optional Device parameter to pin_memory/is_pinned that does nothing (#60201) 2021-06-28 10:38:52 -07:00
config
coverage_plugins_package Strictly type everything in .github and tools (#59117) 2021-06-07 14:49:36 -07:00
fast_nvcc Strictly type everything in .github and tools (#59117) 2021-06-07 14:49:36 -07:00
gdb Strictly type everything in .github and tools (#59117) 2021-06-07 14:49:36 -07:00
jit
linter Refactor clang_tidy.py (#61119) 2021-07-06 16:02:11 -07:00
lite_interpreter Strictly type everything in .github and tools (#59117) 2021-06-07 14:49:36 -07:00
pyi Support __rand__, __ror__ and __rxor__ (#59240) 2021-07-07 13:34:14 -07:00
rules
setup_helpers Fix Error when run python setup.py install again on Windows (#59689) 2021-06-10 12:22:21 -07:00
shared Strictly type everything in .github and tools (#59117) 2021-06-07 14:49:36 -07:00
stats adding a build_start_time_epoch to build meta info (#61322) 2021-07-07 16:27:13 -07:00
test move CI related functions out of run_test.py (#61124) 2021-07-06 09:06:42 -07:00
testing move CI related functions out of run_test.py (#61124) 2021-07-06 09:06:42 -07:00
__init__.py
actions_local_runner.py First step to rearrange files in tools folder (#60473) 2021-06-24 10:13:58 -07:00
build_libtorch.py
build_pytorch_libs.py Strictly type everything in .github and tools (#59117) 2021-06-07 14:49:36 -07:00
build_variables.bzl [JIT] Add torch._C.ScriptList` (#52832) 2021-07-01 20:28:13 -07:00
download_mnist.py Strictly type everything in .github and tools (#59117) 2021-06-07 14:49:36 -07:00
extract_scripts.py
generate_torch_version.py Strictly type everything in .github and tools (#59117) 2021-06-07 14:49:36 -07:00
generated_dirs.txt
git-pre-commit Refactor clang_tidy.py (#61119) 2021-07-06 16:02:11 -07:00
git_add_generated_dirs.sh
git_reset_generated_dirs.sh
nightly.py Strictly type everything in .github and tools (#59117) 2021-06-07 14:49:36 -07:00
pytorch.version
README.md Refactor clang_tidy.py (#61119) 2021-07-06 16:02:11 -07:00
render_junit.py remove unused type: ignore directives (#60006) 2021-06-18 07:23:31 -07:00
vscode_settings.py

This folder contains a number of scripts which are used as part of the PyTorch build process. This directory also doubles as a Python module hierarchy (thus the __init__.py).

Overview

Modern infrastructure:

  • autograd - Code generation for autograd. This includes definitions of all our derivatives.
  • jit - Code generation for JIT
  • shared - Generic infrastructure that scripts in tools may find useful.
    • module_loader.py - Makes it easier to import arbitrary Python files in a script, without having to add them to the PYTHONPATH first.

Legacy infrastructure (we should kill this):

  • cwrap - Implementation of legacy code generation for THNN/THCUNN. This is used by nnwrap.

Build system pieces:

  • setup_helpers - Helper code for searching for third-party dependencies on the user system.
  • build_pytorch_libs.py - cross-platform script that builds all of the constituent libraries of PyTorch, but not the PyTorch Python extension itself.
  • build_libtorch.py - Script for building libtorch, a standalone C++ library without Python support. This build script is tested in CI.
  • fast_nvcc - Mostly-transparent wrapper over nvcc that parallelizes compilation when used to build CUDA files for multiple architectures at once.
    • fast_nvcc.py - Python script, entrypoint to the fast nvcc wrapper.

Developer tools which you might find useful:

  • linter/clang_tidy - Script for running clang-tidy on lines of your script which you changed.
  • extract_scripts.py - Extract scripts from .github/workflows/*.yml into a specified dir, on which linters such as linter/run_shellcheck.sh can be run. Assumes that every run script has shell: bash unless a different shell is explicitly listed on that specific step (so defaults doesn't currently work), but also has some rules for other situations such as actions/github-script. Exits with nonzero status if any of the extracted scripts contain GitHub Actions expressions: ${{<expression> }}
  • git_add_generated_dirs.sh and git_reset_generated_dirs.sh - Use this to force add generated files to your Git index, so that you can conveniently run diffs on them when working on code-generation. (See also generated_dirs.txt which specifies the list of directories with generated files.)
  • linter/mypy_wrapper.py - Run mypy on a single file using the appropriate subset of our mypy*.ini configs.
  • linter/run_shellcheck.sh - Find *.sh files (recursively) in the directories specified as arguments, and run ShellCheck on all of them.
  • stats/test_history.py - Query S3 to display history of a single test across multiple jobs over time.
  • linter/trailing_newlines.py - Take names of UTF-8 files from stdin, print names of nonempty files whose contents don't end in exactly one trailing newline, exit with status 1 if no output printed or 0 if some filenames were printed.
  • linter/translate_annotations.py - Read Flake8 or clang-tidy warnings (according to a --regex) from a --file, convert to the JSON format accepted by pytorch/add-annotations-github-action, and translate line numbers from HEAD back in time to the given --commit by running git diff-index --unified=0 appropriately.
  • vscode_settings.py - Merge .vscode/settings_recommended.json into your workspace-local .vscode/settings.json, preferring the former in case of conflicts but otherwise preserving the latter as much as possible.

Important if you want to run on AMD GPU:

  • amd_build - HIPify scripts, for transpiling CUDA into AMD HIP. Right now, PyTorch and Caffe2 share logic for how to do this transpilation, but have separate entry-points for transpiling either PyTorch or Caffe2 code.
    • build_amd.py - Top-level entry point for HIPifying our codebase.

Tools which are only situationally useful: