Execute C++ based GTest unit tests from a python wrapper #64067
Comments
can I contribute to this? this will be my first, can anybody help me! |
can i also work on this? it will be mine first too, soo can we contribute together @Prashant723 cause i am a begineer too. |
@Akshat1331 ok mail me at gargprashant1@yahoo.com |
hi, i would also like to contribute to this |
Yeah sure we together will contribute on this issue on Monday as I have
some work on hand now.
Thanks & Regards
…On Sat, 28 Aug 2021, 17:09 nikhilsajwan, ***@***.***> wrote:
hi, i would also like to contribute to this
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#64067 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQLMPVQSBTR5GUO5LCMXF7TT7DDH5ANCNFSM5C4MRQHA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
I cant find c++ Gtest, can anyone tell me where are they stored. |
I would love to contribute too! |
haovic
added a commit
to haovic/pytorch
that referenced
this issue
Aug 31, 2021
…pper Summary: This is the beginning of transitioning away from test.sh: pytorch#64067 Moved execution of FileStoreTest, HashStoreTest, TCPStoreTest from test.sh to run_test.py. Since these are compiled tests, the logic of test.sh was just migrated and the tests are run through subprocess. Test Plan: ``` python3 test/run_test.py --include cpp/c10d/FileStoreTest cpp/c10d/HashStoreTest cpp/c10d/TCPStoreTest ``` Wait for CI Differential Revision: D30662844 fbshipit-source-id: 783d908a2d3a97b5e65e8b5d3b28b79e715b1cca
I would like to contribute here. |
would like to contribute |
I would like to contribute |
haovic
added a commit
to haovic/pytorch
that referenced
this issue
Aug 31, 2021
…pper (pytorch#64252) Summary: Pull Request resolved: pytorch#64252 This is the beginning of transitioning away from test.sh: pytorch#64067 Moved execution of FileStoreTest, HashStoreTest, TCPStoreTest from test.sh to run_test.py. Since these are compiled tests, the logic of test.sh was just migrated and the tests are run through subprocess. Test Plan: ``` python3 test/run_test.py --include cpp/c10d/FileStoreTest cpp/c10d/HashStoreTest cpp/c10d/TCPStoreTest ``` Wait for CI Differential Revision: D30662844 fbshipit-source-id: 5ba0d2993e2980c9272f8d627c45ed0965d0483b
haovic
added a commit
to haovic/pytorch
that referenced
this issue
Sep 1, 2021
…pper (pytorch#64252) Summary: Pull Request resolved: pytorch#64252 This is the beginning of transitioning away from test.sh: pytorch#64067 Moved execution of FileStoreTest, HashStoreTest, TCPStoreTest from test.sh to run_test.py. Since these are compiled tests, the logic of test.sh was just migrated and the tests are run through subprocess. Test Plan: ``` python3 test/run_test.py --include cpp/c10d/FileStoreTest cpp/c10d/HashStoreTest cpp/c10d/TCPStoreTest ``` Wait for CI Differential Revision: D30662844 fbshipit-source-id: ea3cb5de079b2916fd3515df9057454223f7c24f
haovic
added a commit
to haovic/pytorch
that referenced
this issue
Sep 1, 2021
…pper (pytorch#64252) Summary: Pull Request resolved: pytorch#64252 This is the beginning of transitioning away from test.sh: pytorch#64067 Moved execution of FileStoreTest, HashStoreTest, TCPStoreTest from test.sh to run_test.py. Since these are compiled tests, the logic of test.sh was just migrated and the tests are run through subprocess. Test Plan: ``` python3 test/run_test.py --include cpp/c10d/FileStoreTest cpp/c10d/HashStoreTest cpp/c10d/TCPStoreTest ``` Wait for CI Differential Revision: D30662844 fbshipit-source-id: fb34f398a6d5de26c11a0cf494991aeafea6b088
haovic
added a commit
to haovic/pytorch
that referenced
this issue
Sep 1, 2021
…pper (pytorch#64252) Summary: Pull Request resolved: pytorch#64252 This is the beginning of transitioning away from test.sh: pytorch#64067 Moved execution of FileStoreTest, HashStoreTest, TCPStoreTest from test.sh to run_test.py. Since these are compiled tests, the logic of test.sh was just migrated and the tests are run through subprocess. Test Plan: ``` python3 test/run_test.py --include cpp/c10d/FileStoreTest cpp/c10d/HashStoreTest cpp/c10d/TCPStoreTest ``` Wait for CI Differential Revision: D30662844 fbshipit-source-id: 49b4ab43353d14dcdf43aaa8d9ae6901bbff04b9
haovic
added a commit
to haovic/pytorch
that referenced
this issue
Sep 8, 2021
…pper (pytorch#64252) Summary: Pull Request resolved: pytorch#64252 This is the beginning of transitioning away from test.sh: pytorch#64067 Moved execution of FileStoreTest, HashStoreTest, TCPStoreTest from test.sh to run_test.py. Since these are compiled tests, the logic of test.sh was just migrated and the tests are run through subprocess. Test Plan: ``` python3 test/run_test.py --include cpp/c10d/FileStoreTest cpp/c10d/HashStoreTest cpp/c10d/TCPStoreTest ``` Wait for CI Differential Revision: D30662844 fbshipit-source-id: 128ab6d932591b6487ce430b5df0df651f4e7792
haovic
added a commit
to haovic/pytorch
that referenced
this issue
Sep 8, 2021
…pper (pytorch#64252) Summary: Pull Request resolved: pytorch#64252 This is the beginning of transitioning away from test.sh: pytorch#64067 Moved execution of FileStoreTest, HashStoreTest, TCPStoreTest from test.sh to run_test.py. Since these are compiled tests, the logic of test.sh was just migrated and the tests are run through subprocess. Test Plan: ``` python3 test/run_test.py --include cpp/c10d/FileStoreTest cpp/c10d/HashStoreTest cpp/c10d/TCPStoreTest ``` Wait for CI Differential Revision: D30662844 fbshipit-source-id: 327f77fa7a2d25a1cfbdc24f358436ca2e197538
haovic
added a commit
to haovic/pytorch
that referenced
this issue
Sep 8, 2021
…pper (pytorch#64252) Summary: Pull Request resolved: pytorch#64252 This is the beginning of transitioning away from test.sh: pytorch#64067 Moved execution of FileStoreTest, HashStoreTest, TCPStoreTest from test.sh to run_test.py. Since these are compiled tests, the logic of test.sh was just migrated and the tests are run through subprocess. Test Plan: ``` python3 test/run_test.py --include cpp/c10d/FileStoreTest cpp/c10d/HashStoreTest cpp/c10d/TCPStoreTest ``` Wait for CI Differential Revision: D30662844 fbshipit-source-id: 184214ffa35ed764f1c8b5fca9d7d4d33a2cc2ee
haovic
added a commit
to haovic/pytorch
that referenced
this issue
Sep 8, 2021
…pper (pytorch#64252) Summary: Pull Request resolved: pytorch#64252 This is the beginning of transitioning away from test.sh: pytorch#64067 Moved execution of FileStoreTest, HashStoreTest, TCPStoreTest from test.sh to run_test.py. Since these are compiled tests, the logic of test.sh was just migrated and the tests are run through subprocess. Test Plan: ``` python3 test/run_test.py --include cpp/c10d/FileStoreTest cpp/c10d/HashStoreTest cpp/c10d/TCPStoreTest ``` Wait for CI Differential Revision: D30662844 fbshipit-source-id: 7566ba6c7d4dc47011368003b96be1f1ee41f778
haovic
added a commit
to haovic/pytorch
that referenced
this issue
Sep 9, 2021
…pper (pytorch#64252) Summary: Pull Request resolved: pytorch#64252 This is the beginning of transitioning away from test.sh: pytorch#64067 Moved execution of FileStoreTest, HashStoreTest, TCPStoreTest from test.sh to run_test.py. Since these are compiled tests, the logic of test.sh was just migrated and the tests are run through subprocess. Test Plan: ``` python3 test/run_test.py --include cpp/c10d/FileStoreTest cpp/c10d/HashStoreTest cpp/c10d/TCPStoreTest ``` Wait for CI Differential Revision: D30662844 fbshipit-source-id: 7eaa189c7fcd6f09b1b4ffdaf1683bd9cd59f445
haovic
added a commit
to haovic/pytorch
that referenced
this issue
Sep 9, 2021
…pper (pytorch#64252) Summary: Pull Request resolved: pytorch#64252 This is the beginning of transitioning away from test.sh: pytorch#64067 Moved execution of FileStoreTest, HashStoreTest, TCPStoreTest from test.sh to run_test.py. Since these are compiled tests, the logic of test.sh was just migrated and the tests are run through subprocess. Test Plan: ``` python3 test/run_test.py --include cpp/c10d/FileStoreTest cpp/c10d/HashStoreTest cpp/c10d/TCPStoreTest ``` Wait for CI Differential Revision: D30662844 fbshipit-source-id: 3807399df05a0f5a08e06f11eba68f602b2bf014
driazati
added a commit
that referenced
this issue
Oct 19, 2021
This adds a Python-based wrapper for running C++ tests intended to be run in CI as part of #64067. Eventually this should replace all manual invocations of running a C++ test in CI. For local development running the binaries manually is still the best UX since you have full control of gtest flags and can avoid Python's startup time. For simple tests that can just be run out-of-the-box, add them to the [allowlist](https://github.com/pytorch/pytorch/pull/65514/files#diff-c9f1a162beb062b5905b0b8ae2a7d39ba453b1a821b62094687dbb8ce67763dbR39). This PR has an example of a more complicated invocation for `test_jit` as well which can be implemented in Python with some custom logic. Differential Revision: [D31296508](https://our.internmc.facebook.com/intern/diff/D31296508) [ghstack-poisoned]
driazati
added a commit
that referenced
this issue
Oct 19, 2021
This adds a Python-based wrapper for running C++ tests intended to be run in CI as part of #64067. Eventually this should replace all manual invocations of running a C++ test in CI. For local development running the binaries manually is still the best UX since you have full control of gtest flags and can avoid Python's startup time. For simple tests that can just be run out-of-the-box, add them to the [allowlist](https://github.com/pytorch/pytorch/pull/65514/files#diff-c9f1a162beb062b5905b0b8ae2a7d39ba453b1a821b62094687dbb8ce67763dbR39). This PR has an example of a more complicated invocation for `test_jit` as well which can be implemented in Python with some custom logic. Differential Revision: [D31296508](https://our.internmc.facebook.com/intern/diff/D31296508) [ghstack-poisoned]
driazati
added a commit
that referenced
this issue
Oct 19, 2021
This adds a Python-based wrapper for running C++ tests intended to be run in CI as part of #64067. Eventually this should replace all manual invocations of running a C++ test in CI. For local development running the binaries manually is still the best UX since you have full control of gtest flags and can avoid Python's startup time. For simple tests that can just be run out-of-the-box, add them to the [allowlist](https://github.com/pytorch/pytorch/pull/65514/files#diff-c9f1a162beb062b5905b0b8ae2a7d39ba453b1a821b62094687dbb8ce67763dbR39). This PR has an example of a more complicated invocation for `test_jit` as well which can be implemented in Python with some custom logic. Differential Revision: [D31296508](https://our.internmc.facebook.com/intern/diff/D31296508) [ghstack-poisoned]
driazati
added a commit
that referenced
this issue
Oct 19, 2021
This adds a Python-based wrapper for running C++ tests intended to be run in CI as part of #64067. Eventually this should replace all manual invocations of running a C++ test in CI. For local development running the binaries manually is still the best UX since you have full control of gtest flags and can avoid Python's startup time. For simple tests that can just be run out-of-the-box, add them to the [allowlist](https://github.com/pytorch/pytorch/pull/65514/files#diff-c9f1a162beb062b5905b0b8ae2a7d39ba453b1a821b62094687dbb8ce67763dbR39). This PR has an example of a more complicated invocation for `test_jit` as well which can be implemented in Python with some custom logic. Differential Revision: [D31296508](https://our.internmc.facebook.com/intern/diff/D31296508) [ghstack-poisoned]
driazati
added a commit
that referenced
this issue
Oct 20, 2021
This adds a Python-based wrapper for running C++ tests intended to be run in CI as part of #64067. Eventually this should replace all manual invocations of running a C++ test in CI. For local development running the binaries manually is still the best UX since you have full control of gtest flags and can avoid Python's startup time. For simple tests that can just be run out-of-the-box, add them to the [allowlist](https://github.com/pytorch/pytorch/pull/65514/files#diff-c9f1a162beb062b5905b0b8ae2a7d39ba453b1a821b62094687dbb8ce67763dbR39). This PR has an example of a more complicated invocation for `test_jit` as well which can be implemented in Python with some custom logic. Differential Revision: [D31296508](https://our.internmc.facebook.com/intern/diff/D31296508) [ghstack-poisoned]
driazati
added a commit
that referenced
this issue
Oct 20, 2021
This adds a Python-based wrapper for running C++ tests intended to be run in CI as part of #64067. Eventually this should replace all manual invocations of running a C++ test in CI. For local development running the binaries manually is still the best UX since you have full control of gtest flags and can avoid Python's startup time. For simple tests that can just be run out-of-the-box, add them to the [allowlist](https://github.com/pytorch/pytorch/pull/65514/files#diff-c9f1a162beb062b5905b0b8ae2a7d39ba453b1a821b62094687dbb8ce67763dbR39). This PR has an example of a more complicated invocation for `test_jit` as well which can be implemented in Python with some custom logic. Differential Revision: [D31296508](https://our.internmc.facebook.com/intern/diff/D31296508) [ghstack-poisoned]
driazati
added a commit
that referenced
this issue
Oct 20, 2021
This adds a Python-based wrapper for running C++ tests intended to be run in CI as part of #64067. Eventually this should replace all manual invocations of running a C++ test in CI. For local development running the binaries manually is still the best UX since you have full control of gtest flags and can avoid Python's startup time. For simple tests that can just be run out-of-the-box, add them to the [allowlist](https://github.com/pytorch/pytorch/pull/65514/files#diff-c9f1a162beb062b5905b0b8ae2a7d39ba453b1a821b62094687dbb8ce67763dbR39). This PR has an example of a more complicated invocation for `test_jit` as well which can be implemented in Python with some custom logic. Differential Revision: [D31296508](https://our.internmc.facebook.com/intern/diff/D31296508) [ghstack-poisoned]
driazati
added a commit
that referenced
this issue
Oct 20, 2021
This adds a Python-based wrapper for running C++ tests intended to be run in CI as part of #64067. Eventually this should replace all manual invocations of running a C++ test in CI. For local development running the binaries manually is still the best UX since you have full control of gtest flags and can avoid Python's startup time. For simple tests that can just be run out-of-the-box, add them to the [allowlist](https://github.com/pytorch/pytorch/pull/65514/files#diff-c9f1a162beb062b5905b0b8ae2a7d39ba453b1a821b62094687dbb8ce67763dbR39). This PR has an example of a more complicated invocation for `test_jit` as well which can be implemented in Python with some custom logic. Differential Revision: [D31296508](https://our.internmc.facebook.com/intern/diff/D31296508) [ghstack-poisoned]
driazati
added a commit
that referenced
this issue
Oct 21, 2021
This adds a Python-based wrapper for running C++ tests intended to be run in CI as part of #64067. Eventually this should replace all manual invocations of running a C++ test in CI. For local development running the binaries manually is still the best UX since you have full control of gtest flags and can avoid Python's startup time. For simple tests that can just be run out-of-the-box, add them to the [allowlist](https://github.com/pytorch/pytorch/pull/65514/files#diff-c9f1a162beb062b5905b0b8ae2a7d39ba453b1a821b62094687dbb8ce67763dbR39). This PR has an example of a more complicated invocation for `test_jit` as well which can be implemented in Python with some custom logic. Differential Revision: [D31296508](https://our.internmc.facebook.com/intern/diff/D31296508) [ghstack-poisoned]
driazati
added a commit
that referenced
this issue
Oct 21, 2021
This adds a Python-based wrapper for running C++ tests intended to be run in CI as part of #64067. Eventually this should replace all manual invocations of running a C++ test in CI. For local development running the binaries manually is still the best UX since you have full control of gtest flags and can avoid Python's startup time. For simple tests that can just be run out-of-the-box, add them to the [allowlist](https://github.com/pytorch/pytorch/pull/65514/files#diff-c9f1a162beb062b5905b0b8ae2a7d39ba453b1a821b62094687dbb8ce67763dbR39). This PR has an example of a more complicated invocation for `test_jit` as well which can be implemented in Python with some custom logic. Differential Revision: [D31296508](https://our.internmc.facebook.com/intern/diff/D31296508) [ghstack-poisoned]
driazati
added a commit
that referenced
this issue
Oct 21, 2021
This adds a Python-based wrapper for running C++ tests intended to be run in CI as part of #64067. Eventually this should replace all manual invocations of running a C++ test in CI. For local development running the binaries manually is still the best UX since you have full control of gtest flags and can avoid Python's startup time. For simple tests that can just be run out-of-the-box, add them to the [allowlist](https://github.com/pytorch/pytorch/pull/65514/files#diff-c9f1a162beb062b5905b0b8ae2a7d39ba453b1a821b62094687dbb8ce67763dbR39). This PR has an example of a more complicated invocation for `test_jit` as well which can be implemented in Python with some custom logic. Differential Revision: [D31296508](https://our.internmc.facebook.com/intern/diff/D31296508) [ghstack-poisoned]
driazati
added a commit
that referenced
this issue
Oct 21, 2021
This adds a Python-based wrapper for running C++ tests intended to be run in CI as part of #64067. Eventually this should replace all manual invocations of running a C++ test in CI. For local development running the binaries manually is still the best UX since you have full control of gtest flags and can avoid Python's startup time. For simple tests that can just be run out-of-the-box, add them to the [allowlist](https://github.com/pytorch/pytorch/pull/65514/files#diff-c9f1a162beb062b5905b0b8ae2a7d39ba453b1a821b62094687dbb8ce67763dbR39). This PR has an example of a more complicated invocation for `test_jit` as well which can be implemented in Python with some custom logic. Differential Revision: [D31296508](https://our.internmc.facebook.com/intern/diff/D31296508) [ghstack-poisoned]
driazati
added a commit
that referenced
this issue
Oct 21, 2021
This adds a Python-based wrapper for running C++ tests intended to be run in CI as part of #64067. Eventually this should replace all manual invocations of running a C++ test in CI. For local development running the binaries manually is still the best UX since you have full control of gtest flags and can avoid Python's startup time. For simple tests that can just be run out-of-the-box, add them to the [allowlist](https://github.com/pytorch/pytorch/pull/65514/files#diff-c9f1a162beb062b5905b0b8ae2a7d39ba453b1a821b62094687dbb8ce67763dbR39). This PR has an example of a more complicated invocation for `test_jit` as well which can be implemented in Python with some custom logic. Differential Revision: [D31296508](https://our.internmc.facebook.com/intern/diff/D31296508) [ghstack-poisoned]
driazati
added a commit
that referenced
this issue
Oct 21, 2021
This adds a Python-based wrapper for running C++ tests intended to be run in CI as part of #64067. Eventually this should replace all manual invocations of running a C++ test in CI. For local development running the binaries manually is still the best UX since you have full control of gtest flags and can avoid Python's startup time. For simple tests that can just be run out-of-the-box, add them to the [allowlist](https://github.com/pytorch/pytorch/pull/65514/files#diff-c9f1a162beb062b5905b0b8ae2a7d39ba453b1a821b62094687dbb8ce67763dbR39). This PR has an example of a more complicated invocation for `test_jit` as well which can be implemented in Python with some custom logic. Differential Revision: [D31296508](https://our.internmc.facebook.com/intern/diff/D31296508) [ghstack-poisoned]
driazati
added a commit
that referenced
this issue
Oct 21, 2021
This adds a Python-based wrapper for running C++ tests intended to be run in CI as part of #64067. Eventually this should replace all manual invocations of running a C++ test in CI. For local development running the binaries manually is still the best UX since you have full control of gtest flags and can avoid Python's startup time. For simple tests that can just be run out-of-the-box, add them to the [allowlist](https://github.com/pytorch/pytorch/pull/65514/files#diff-c9f1a162beb062b5905b0b8ae2a7d39ba453b1a821b62094687dbb8ce67763dbR39). This PR has an example of a more complicated invocation for `test_jit` as well which can be implemented in Python with some custom logic. Differential Revision: [D31296508](https://our.internmc.facebook.com/intern/diff/D31296508) [ghstack-poisoned]
driazati
added a commit
that referenced
this issue
Oct 21, 2021
This adds a Python-based wrapper for running C++ tests intended to be run in CI as part of #64067. Eventually this should replace all manual invocations of running a C++ test in CI. For local development running the binaries manually is still the best UX since you have full control of gtest flags and can avoid Python's startup time. For simple tests that can just be run out-of-the-box, add them to the [allowlist](https://github.com/pytorch/pytorch/pull/65514/files#diff-c9f1a162beb062b5905b0b8ae2a7d39ba453b1a821b62094687dbb8ce67763dbR39). This PR has an example of a more complicated invocation for `test_jit` as well which can be implemented in Python with some custom logic. Differential Revision: [D31296508](https://our.internmc.facebook.com/intern/diff/D31296508) [ghstack-poisoned]
driazati
added a commit
that referenced
this issue
Oct 22, 2021
This adds a Python-based wrapper for running C++ tests intended to be run in CI as part of #64067. Eventually this should replace all manual invocations of running a C++ test in CI. For local development running the binaries manually is still the best UX since you have full control of gtest flags and can avoid Python's startup time. For simple tests that can just be run out-of-the-box, add them to the [allowlist](https://github.com/pytorch/pytorch/pull/65514/files#diff-c9f1a162beb062b5905b0b8ae2a7d39ba453b1a821b62094687dbb8ce67763dbR39). This PR has an example of a more complicated invocation for `test_jit` as well which can be implemented in Python with some custom logic. Differential Revision: [D31296508](https://our.internmc.facebook.com/intern/diff/D31296508) [ghstack-poisoned]
driazati
added a commit
that referenced
this issue
Oct 22, 2021
This adds a Python-based wrapper for running C++ tests intended to be run in CI as part of #64067. Eventually this should replace all manual invocations of running a C++ test in CI. For local development running the binaries manually is still the best UX since you have full control of gtest flags and can avoid Python's startup time. For simple tests that can just be run out-of-the-box, add them to the [allowlist](https://github.com/pytorch/pytorch/pull/65514/files#diff-c9f1a162beb062b5905b0b8ae2a7d39ba453b1a821b62094687dbb8ce67763dbR39). This PR has an example of a more complicated invocation for `test_jit` as well which can be implemented in Python with some custom logic. Differential Revision: [D31296508](https://our.internmc.facebook.com/intern/diff/D31296508) [ghstack-poisoned]
driazati
added a commit
that referenced
this issue
Oct 22, 2021
This adds a Python-based wrapper for running C++ tests intended to be run in CI as part of #64067. Eventually this should replace all manual invocations of running a C++ test in CI. For local development running the binaries manually is still the best UX since you have full control of gtest flags and can avoid Python's startup time. For simple tests that can just be run out-of-the-box, add them to the [allowlist](https://github.com/pytorch/pytorch/pull/65514/files#diff-c9f1a162beb062b5905b0b8ae2a7d39ba453b1a821b62094687dbb8ce67763dbR39). This PR has an example of a more complicated invocation for `test_jit` as well which can be implemented in Python with some custom logic. Differential Revision: [D31296508](https://our.internmc.facebook.com/intern/diff/D31296508) [ghstack-poisoned]
driazati
added a commit
that referenced
this issue
Oct 22, 2021
This adds a Python-based wrapper for running C++ tests intended to be run in CI as part of #64067. Eventually this should replace all manual invocations of running a C++ test in CI. For local development running the binaries manually is still the best UX since you have full control of gtest flags and can avoid Python's startup time. For simple tests that can just be run out-of-the-box, add them to the [allowlist](https://github.com/pytorch/pytorch/pull/65514/files#diff-c9f1a162beb062b5905b0b8ae2a7d39ba453b1a821b62094687dbb8ce67763dbR39). This PR has an example of a more complicated invocation for `test_jit` as well which can be implemented in Python with some custom logic. Differential Revision: [D31296508](https://our.internmc.facebook.com/intern/diff/D31296508) [ghstack-poisoned]
driazati
added a commit
that referenced
this issue
Oct 23, 2021
This adds a Python-based wrapper for running C++ tests intended to be run in CI as part of #64067. Eventually this should replace all manual invocations of running a C++ test in CI. For local development running the binaries manually is still the best UX since you have full control of gtest flags and can avoid Python's startup time. For simple tests that can just be run out-of-the-box, add them to the [allowlist](https://github.com/pytorch/pytorch/pull/65514/files#diff-c9f1a162beb062b5905b0b8ae2a7d39ba453b1a821b62094687dbb8ce67763dbR39). This PR has an example of a more complicated invocation for `test_jit` as well which can be implemented in Python with some custom logic. Differential Revision: [D31296508](https://our.internmc.facebook.com/intern/diff/D31296508) [ghstack-poisoned]
driazati
added a commit
that referenced
this issue
Oct 23, 2021
This adds a Python-based wrapper for running C++ tests intended to be run in CI as part of #64067. Eventually this should replace all manual invocations of running a C++ test in CI. For local development running the binaries manually is still the best UX since you have full control of gtest flags and can avoid Python's startup time. For simple tests that can just be run out-of-the-box, add them to the [allowlist](https://github.com/pytorch/pytorch/pull/65514/files#diff-c9f1a162beb062b5905b0b8ae2a7d39ba453b1a821b62094687dbb8ce67763dbR39). This PR has an example of a more complicated invocation for `test_jit` as well which can be implemented in Python with some custom logic. Differential Revision: [D31296508](https://our.internmc.facebook.com/intern/diff/D31296508) [ghstack-poisoned]
driazati
added a commit
that referenced
this issue
Oct 23, 2021
This adds a Python-based wrapper for running C++ tests intended to be run in CI as part of #64067. Eventually this should replace all manual invocations of running a C++ test in CI. For local development running the binaries manually is still the best UX since you have full control of gtest flags and can avoid Python's startup time. For simple tests that can just be run out-of-the-box, add them to the [allowlist](https://github.com/pytorch/pytorch/pull/65514/files#diff-c9f1a162beb062b5905b0b8ae2a7d39ba453b1a821b62094687dbb8ce67763dbR39). This PR has an example of a more complicated invocation for `test_jit` as well which can be implemented in Python with some custom logic. Differential Revision: [D31296508](https://our.internmc.facebook.com/intern/diff/D31296508) [ghstack-poisoned]
driazati
added a commit
that referenced
this issue
Oct 23, 2021
This adds a Python-based wrapper for running C++ tests intended to be run in CI as part of #64067. Eventually this should replace all manual invocations of running a C++ test in CI. For local development running the binaries manually is still the best UX since you have full control of gtest flags and can avoid Python's startup time. For simple tests that can just be run out-of-the-box, add them to the [allowlist](https://github.com/pytorch/pytorch/pull/65514/files#diff-c9f1a162beb062b5905b0b8ae2a7d39ba453b1a821b62094687dbb8ce67763dbR39). This PR has an example of a more complicated invocation for `test_jit` as well which can be implemented in Python with some custom logic. Differential Revision: [D31296508](https://our.internmc.facebook.com/intern/diff/D31296508) [ghstack-poisoned]
driazati
added a commit
that referenced
this issue
Oct 23, 2021
This adds a Python-based wrapper for running C++ tests intended to be run in CI as part of #64067. Eventually this should replace all manual invocations of running a C++ test in CI. For local development running the binaries manually is still the best UX since you have full control of gtest flags and can avoid Python's startup time. For simple tests that can just be run out-of-the-box, add them to the [allowlist](https://github.com/pytorch/pytorch/pull/65514/files#diff-c9f1a162beb062b5905b0b8ae2a7d39ba453b1a821b62094687dbb8ce67763dbR39). This PR has an example of a more complicated invocation for `test_jit` as well which can be implemented in Python with some custom logic. Differential Revision: [D31296508](https://our.internmc.facebook.com/intern/diff/D31296508) [ghstack-poisoned]
driazati
added a commit
that referenced
this issue
Oct 23, 2021
This adds a Python-based wrapper for running C++ tests intended to be run in CI as part of #64067. Eventually this should replace all manual invocations of running a C++ test in CI. For local development running the binaries manually is still the best UX since you have full control of gtest flags and can avoid Python's startup time. For simple tests that can just be run out-of-the-box, add them to the [allowlist](https://github.com/pytorch/pytorch/pull/65514/files#diff-c9f1a162beb062b5905b0b8ae2a7d39ba453b1a821b62094687dbb8ce67763dbR39). This PR has an example of a more complicated invocation for `test_jit` as well which can be implemented in Python with some custom logic. Differential Revision: [D31296508](https://our.internmc.facebook.com/intern/diff/D31296508) [ghstack-poisoned]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Motivation
Currently lots of C++ based unit tests are executed directly from test.sh/win-test.sh for example:
pytorch/.jenkins/pytorch/test.sh
Line 317 in 0bd8d09
Which have following drawbacks:
win-test.sh
andtest.sh
are two different files)--gtest_output
) argumentPitch
Add a .json file with all C++ GTest based tests or just add them directly to run_test.py akin to
pytorch/test/run_test.py
Line 53 in 0bd8d09
This would allow our auto-sharding system to balance them correctly across the shards, continue execution over failed tests as well as using re-using some of standard decorators for excluding test runs on certain configurations
cc @ezyang @seemethere @malfet @walterddr @lg20987 @pytorch/pytorch-dev-infra
The text was updated successfully, but these errors were encountered: