using PR number instead of IN_PULL_REQUEST (#63360)
authorRong Rong (AI Infra) <rongr@fb.com>
Wed, 18 Aug 2021 22:02:05 +0000 (15:02 -0700)
committerFacebook GitHub Bot <facebook-github-bot@users.noreply.github.com>
Wed, 18 Aug 2021 22:05:10 +0000 (15:05 -0700)
commit15eec8e1d1ea5b3354bc305f1afe0c01a64ea748
treeb4bc0b9fb623e1a7f1c9f956fdbbc12556d77b64
parent779a3d47b0c057211374a9c4128fbdf78acee4c9
using PR number instead of IN_PULL_REQUEST (#63360)

Summary:
PR numbers should be available on GHA after this.

This fixes some target determinator not working issue discovered when manually running: https://github.com/pytorch/pytorch/issues/63412.

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

Reviewed By: malfet, zhouzhuojie, seemethere

Differential Revision: D30374615

Pulled By: walterddr

fbshipit-source-id: eee8d8bb7aa4308a6a50cfdcd4423a96d846777f
.circleci/config.yml
.circleci/verbatim-sources/job-specs/pytorch-job-specs.yml
.github/templates/linux_ci_workflow.yml.j2
.github/workflows/generated-linux-bionic-cuda10.2-py3.9-gcc7.yml
.github/workflows/generated-linux-bionic-py3.8-gcc9-coverage.yml
.github/workflows/generated-linux-xenial-cuda10.2-py3.6-gcc7.yml
.github/workflows/generated-linux-xenial-cuda11.1-py3.6-gcc7.yml
.github/workflows/generated-linux-xenial-py3.6-gcc5.4.yml
.github/workflows/generated-periodic-linux-xenial-cuda11.3-py3.6-gcc7.yml
.jenkins/pytorch/test.sh