# testing **URL:** https://dev-discuss.pytorch.org/c/testing/24.md [Latest](https://dev-discuss.pytorch.org/latest.md) · [Categories](https://dev-discuss.pytorch.org/categories.md) --- ## [About the testing category](https://dev-discuss.pytorch.org/t/about-the-testing-category/35)
**Author:** [@smth](https://dev-discuss.pytorch.org/u/smth)\ **Replies:** 0
--- ## [Proposal: Streamlining PyTorch Test Suite for Multi-Accelerator Reuse](https://dev-discuss.pytorch.org/t/proposal-streamlining-pytorch-test-suite-for-multi-accelerator-reuse/3391)
**Author:** [@fffrog](https://dev-discuss.pytorch.org/u/fffrog)\ **Replies:** 0\ **Last updated:** [May 29, 2026, 4:38am UTC](https://dev-discuss.pytorch.org/t/proposal-streamlining-pytorch-test-suite-for-multi-accelerator-reuse/3391 "2026-05-29T04:38:13Z")
Hi everyone, We have officially kicked off a coordinated initiative to refactor the PyTorch test suite. The core goal is to break the tight coupling between existing test cases and specific hardware, systematically cate… --- ## [Making PyTorch Test Suite usable from out-of-tree braindump](https://dev-discuss.pytorch.org/t/making-pytorch-test-suite-usable-from-out-of-tree-braindump/3357)
**Author:** [@mikaylagawarecki](https://dev-discuss.pytorch.org/u/mikaylagawarecki)\ **Replies:** 1\ **Last updated:** [April 27, 2026, 3:39am UTC](https://dev-discuss.pytorch.org/t/making-pytorch-test-suite-usable-from-out-of-tree-braindump/3357 "2026-04-27T03:39:17Z")
The purpose of this post is to brain-dump any context I had related to making the pytorch test suite device-generic as I am unfortunately moving teams out of PyTorch due to some reshuffling and will not be able to help d… --- ## [Eigendecomposition tests](https://dev-discuss.pytorch.org/t/eigendecomposition-tests/3254)
**Author:** [@Johannes99](https://dev-discuss.pytorch.org/u/Johannes99)\ **Replies:** 1\ **Last updated:** [October 23, 2025, 4:58pm UTC](https://dev-discuss.pytorch.org/t/eigendecomposition-tests/3254 "2025-10-23T16:58:12Z")
Hi!, I am currently working on integrating the new CuSolver XGeev Eigendecomposition into PyTorch. As my code is mostly working, I have moved on to testing. Now I did some testing on my own. I mainly checked if the ei… --- ## [1 High-Security vulnerability found in Black Duck scan](https://dev-discuss.pytorch.org/t/1-high-security-vulnerability-found-in-black-duck-scan/2509)
**Author:** [@doug091](https://dev-discuss.pytorch.org/u/doug091)\ **Replies:** 4\ **Last updated:** [October 3, 2024, 6:09pm UTC](https://dev-discuss.pytorch.org/t/1-high-security-vulnerability-found-in-black-duck-scan/2509 "2024-10-03T18:09:30Z")
Hello! I’m using PyTorch on a project that uses pre-trained AI models. The previous version was 2.2.2, so I updated to version 2.4.1 (current) due to the Black Duck scan reporting that the library was a high-security ri… --- ## [How to test properly?](https://dev-discuss.pytorch.org/t/how-to-test-properly/2492)
**Author:** [@NiklasZ](https://dev-discuss.pytorch.org/u/NiklasZ)\ **Replies:** 1\ **Last updated:** [September 25, 2024, 9:40pm UTC](https://dev-discuss.pytorch.org/t/how-to-test-properly/2492 "2024-09-25T21:40:36Z")
Hi, I’m pretty new to making code contributions on this project and am a bit at a loss as to how to test my PRs properly. I’ve read the contributer guide and run python test/run\_test.py, but am having the following issu… --- ## [Lintrunner changes mypy config somehow, type checks likely broken](https://dev-discuss.pytorch.org/t/lintrunner-changes-mypy-config-somehow-type-checks-likely-broken/2374)
**Author:** [@DeinAlptraum](https://dev-discuss.pytorch.org/u/DeinAlptraum)\ **Replies:** 2\ **Last updated:** [August 11, 2024, 9:16pm UTC](https://dev-discuss.pytorch.org/t/lintrunner-changes-mypy-config-somehow-type-checks-likely-broken/2374 "2024-08-11T21:16:45Z")
I’ve recently setup torch for contributing, and as I wanted to contribute to type annotations, looked into running mypy. To my surprise, I found 17 typing errors just by running mypy in the repo root, so I went to find o… --- ## [Alternatives for compiling C++ on a Macbook Pro with Intel x86\_64?](https://dev-discuss.pytorch.org/t/alternatives-for-compiling-c-on-a-macbook-pro-with-intel-x86-64/1773)
**Author:** [@lamroger](https://dev-discuss.pytorch.org/u/lamroger)\ **Replies:** 5\ **Last updated:** [January 11, 2024, 10:15pm UTC](https://dev-discuss.pytorch.org/t/alternatives-for-compiling-c-on-a-macbook-pro-with-intel-x86-64/1773 "2024-01-11T22:15:26Z")
I was trying to look into the C++ code to fix a bug but couldn’t get a full compile without an error. I did try with some flags to short circuit some potentially unnecessary parts but ended up with the same errors. DEBU… --- ## [Main failing unit test (DynamicShapesMiscTests)](https://dev-discuss.pytorch.org/t/main-failing-unit-test-dynamicshapesmisctests/1607)
**Author:** [@bobbym](https://dev-discuss.pytorch.org/u/bobbym)\ **Replies:** 2\ **Last updated:** [October 25, 2023, 8:20pm UTC](https://dev-discuss.pytorch.org/t/main-failing-unit-test-dynamicshapesmisctests/1607 "2023-10-25T20:20:34Z")
I’m new, and got the build to succeed, but upon running all unit tests (latest main) I get this output : =========================== short test summary info ============================ FAILED \[1.9635s\] dynamo/test\_dyn… --- ## [Addressing Test hole for PrimTorch decomposition operators](https://dev-discuss.pytorch.org/t/addressing-test-hole-for-primtorch-decomposition-operators/1336)
**Author:** [@ekamiti](https://dev-discuss.pytorch.org/u/ekamiti)\ **Replies:** 3\ **Last updated:** [July 25, 2023, 11:42pm UTC](https://dev-discuss.pytorch.org/t/addressing-test-hole-for-primtorch-decomposition-operators/1336 "2023-07-25T23:42:30Z")
I just worked on an issue addressing mismatched behavior of an operator between compiled and eager modes. While implementing the test to verify the fix I noticed not all operator groupings in common\_methods\_invocations.p… --- ## [Nightly Tests on more GPUs](https://dev-discuss.pytorch.org/t/nightly-tests-on-more-gpus/1012)
**Author:** [@harishneit](https://dev-discuss.pytorch.org/u/harishneit)\ **Replies:** 2\ **Last updated:** [March 7, 2023, 5:58pm UTC](https://dev-discuss.pytorch.org/t/nightly-tests-on-more-gpus/1012 "2023-03-07T17:58:01Z")
Greetings from AWS, I work with the PyTorch team at AWS, we are interested in testing & validating Inductor’s support for the GPU hardware we offer to customers on AWS. I went through the integration tests & see that A… --- ## [Changes in Total Test Time](https://dev-discuss.pytorch.org/t/changes-in-total-test-time/716)
**Author:** [@clee2000](https://dev-discuss.pytorch.org/u/clee2000)\ **Replies:** 0\ **Last updated:** [August 1, 2022, 6:40pm UTC](https://dev-discuss.pytorch.org/t/changes-in-total-test-time/716 "2022-08-01T18:40:52Z")
Changes in Total Test Time As PyTorch gains contributors and increases in commit frequency, TTS and job durations become more important to developers who need to iterate and merge their changes. However, as PyTorch grows… --- ## [On Autograd debug asserts, their importance and link to Tensor subclasses](https://dev-discuss.pytorch.org/t/on-autograd-debug-asserts-their-importance-and-link-to-tensor-subclasses/655)
**Author:** [@albanD](https://dev-discuss.pytorch.org/u/albanD)\ **Replies:** 4\ **Last updated:** [June 22, 2022, 8:50pm UTC](https://dev-discuss.pytorch.org/t/on-autograd-debug-asserts-their-importance-and-link-to-tensor-subclasses/655 "2022-06-22T20:50:20Z")
Some background The autograd codegen (that lives in tools/autograd/\*) is responsible for generating a lot of code. Even though some of this scope is not related to autograd (at all) and it is more located in this place f… --- ## [Found something risky in unit test which may cause case failure](https://dev-discuss.pytorch.org/t/found-something-risky-in-unit-test-which-may-cause-case-failure/641)
**Author:** [@huitianbai](https://dev-discuss.pytorch.org/u/huitianbai)\ **Replies:** 0\ **Last updated:** [June 14, 2022, 7:25am UTC](https://dev-discuss.pytorch.org/t/found-something-risky-in-unit-test-which-may-cause-case-failure/641 "2022-06-14T07:25:29Z")
Take case ‘python test\_cuda.py TestCuda.test\_autocast\_methods\_fp32’ for example. It firstly triggers the initialization of ‘AutocastTestLists’ where many ops with different args are built. See it in Pytorch/torch/testi… --- ## [OpInfos in PyTorch 1.10](https://dev-discuss.pytorch.org/t/opinfos-in-pytorch-1-10/253)
**Author:** [@mruberry](https://dev-discuss.pytorch.org/u/mruberry)\ **Replies:** 3\ **Last updated:** [November 6, 2021, 11:37am UTC](https://dev-discuss.pytorch.org/t/opinfos-in-pytorch-1-10/253 "2021-11-06T11:37:32Z")
Hey PyTorch developers! This note is an update on OpInfos, their goals, and planned future work. If you have feedback on OpInfos or you’d like to request a new OpInfo feature then please respond to this post! OpInfos T…