🔗 Helpful links

• 🧪  See artifacts and rendered test results at hud.pytorch.org/pr/74690
• ↩️  [fb-only] Re-run with SSH instructions
• Need help or want to give feedback on the CI? Visit our office hours

💊 CI failures summary and remediations

As of commit 48ce58f (more details on the Dr. CI page):

• 1/1 failures introduced in this PR

🕵️ 1 new failure recognized by patterns

The following CI failures do not appear to be due to upstream breakages:

periodic / win-vs2019-cuda11.5-py3 / test (default, 2, 2, windows.8xlarge.nvidia.gpu) (1/1)

Step: "Test" (full log | diagnosis details | 🔁 rerun)

2022-03-24T21:09:12.3285575Z Generated XML report: test-reports\dist-gloo\test_torch\TEST-TestVitalSignsCudaCUDA-20220324205953.xml
2022-03-24T21:09:12.3287391Z Generated XML report: test-reports\dist-gloo\test_torch\TEST-TestVitalSignsCudaCPU-20220324205953.xml
2022-03-24T21:09:28.6667452Z [TORCH_VITAL] CUDA.used		 true
2022-03-24T21:09:28.6668303Z [TORCH_VITAL] Dataloader.basic_unit_test		 TEST_VALUE_STRING
2022-03-24T21:09:28.6669063Z [TORCH_VITAL] Dataloader.enabled		 True
2022-03-24T21:09:29.2271808Z Traceback (most recent call last):
2022-03-24T21:09:29.2304256Z   File "run_test.py", line 1054, in <module>
2022-03-24T21:09:29.2304861Z     main()
2022-03-24T21:09:29.2305722Z   File "run_test.py", line 1032, in main
2022-03-24T21:09:29.2306334Z     raise RuntimeError(err_message)
2022-03-24T21:09:29.2306956Z RuntimeError: test_torch failed!
2022-03-24T21:09:32.0591741Z 
2022-03-24T21:09:32.0596114Z (base) C:\actions-runner\_work\pytorch\pytorch\test>popd
2022-03-24T21:09:32.0647204Z 
2022-03-24T21:09:32.0667351Z (base) C:\actions-runner\_work\pytorch\pytorch>if ERRORLEVEL 1 exit /b 1 
2022-03-24T21:09:32.2169636Z + cleanup
2022-03-24T21:09:32.2186969Z + retcode=1
2022-03-24T21:09:32.2187443Z + set +x
2022-03-24T21:09:32.3253659Z ##[error]Process completed with exit code 1.
2022-03-24T21:09:33.2292955Z ##[group]Run pytorch/pytorch/.github/actions/upload-test-artifacts@master
2022-03-24T21:09:33.2293946Z with:

@b0noI has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

@pytorchbot merge this

Merge failed due to PR 74690 does not match merge rules
Raised by https://github.com/pytorch/pytorch/actions/runs/2036450019

@pytorchbot force merge this

Merge failed due to PR 74690 does not match merge rules
Raised by https://github.com/pytorch/pytorch/actions/runs/2036458484

Hey @b0noI.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.

Instead of hacking requirements.txt to continue to support an obsolete version of Sphinx with known issues (#60979), why not use modern Sphinx (#70309)?

Instead of hacking requirements.txt to continue to support an obsolete version of Sphinx with known issues (#60979), why not use modern Sphinx (#70309)?

If you can keep no_grad option in place, I'm more than ready to move to new version of sphinx