-
Notifications
You must be signed in to change notification settings - Fork 616
Split neutron backend test based on executor dependency #11934
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/11934
Note: Links to docs will display an error until the docs builds have been completed. ❌ 2 Cancelled Jobs, 1 Unrelated FailureAs of commit 9df4df7 with merge base f9a3ca8 ( CANCELLED JOBS - The following jobs were cancelled. Please retry:
BROKEN TRUNK - The following job failed but were present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This pull request was exported from Phabricator. Differential Revision: D77248751 |
@pytorchbot label "release notes: none" |
This pull request was exported from Phabricator. Differential Revision: D77248751 |
Summary: Pull Request resolved: pytorch#11934 The current test_neutron_backend has a hard requirement on tflite due to the Executor comparing the output. Not all systems have tflite, but we would like to have a sanity check on the backend still. To achieve this, this PR splits the existing test into two files test_neutron_backend contains the tests that do not use any Executor logic (ie, no end to end comparison of outputs) test_neutron_backend_executor contains the rest of the tests. Differential Revision: D77248751
d245519
to
248c5e7
Compare
In general looks good to me. How do you plan to execute tests only in particular files? I believe pytest will fail to run anything if there's at least single file with problematic import. Only working solutions how to execute this are imho 1) single file's tests execution 2) predefined list of "files with supported tests". Please rebase to main to include nxp-unittest workflow. |
This is an issue specific to our internal workflow, which does not use the OSS flow but uses BUCK entirely. So, you just only include the files you want in your BUCK target, very easy (basically a special form of your #2 suggestion). Will rebase |
This pull request was exported from Phabricator. Differential Revision: D77248751 |
248c5e7
to
5d36490
Compare
Summary: Pull Request resolved: pytorch#11934 The current test_neutron_backend has a hard requirement on tflite due to the Executor comparing the output. Not all systems have tflite, but we would like to have a sanity check on the backend still. To achieve this, this PR splits the existing test into two files test_neutron_backend contains the tests that do not use any Executor logic (ie, no end to end comparison of outputs) test_neutron_backend_executor contains the rest of the tests. Differential Revision: D77248751
This pull request was exported from Phabricator. Differential Revision: D77248751 |
Summary: Pull Request resolved: pytorch#11934 The current test_neutron_backend has a hard requirement on tflite due to the Executor comparing the output. Not all systems have tflite, but we would like to have a sanity check on the backend still. To achieve this, this PR splits the existing test into two files test_neutron_backend contains the tests that do not use any Executor logic (ie, no end to end comparison of outputs) test_neutron_backend_executor contains the rest of the tests. Differential Revision: D77248751
5d36490
to
95d08e6
Compare
Summary: Pull Request resolved: pytorch#11934 The current test_neutron_backend has a hard requirement on tflite due to the Executor comparing the output. Not all systems have tflite, but we would like to have a sanity check on the backend still. To achieve this, this PR splits the existing test into two files test_neutron_backend contains the tests that do not use any Executor logic (ie, no end to end comparison of outputs) test_neutron_backend_executor contains the rest of the tests. Differential Revision: D77248751
This pull request was exported from Phabricator. Differential Revision: D77248751 |
Summary: Pull Request resolved: pytorch#11934 The current test_neutron_backend has a hard requirement on tflite due to the Executor comparing the output. Not all systems have tflite, but we would like to have a sanity check on the backend still. To achieve this, this PR splits the existing test into two files test_neutron_backend contains the tests that do not use any Executor logic (ie, no end to end comparison of outputs) test_neutron_backend_executor contains the rest of the tests. Differential Revision: D77248751
95d08e6
to
5815e77
Compare
This pull request was exported from Phabricator. Differential Revision: D77248751 |
Summary: Pull Request resolved: pytorch#11934 The current test_neutron_backend has a hard requirement on tflite due to the Executor comparing the output. Not all systems have tflite, but we would like to have a sanity check on the backend still. To achieve this, this PR splits the existing test into two files test_neutron_backend contains the tests that do not use any Executor logic (ie, no end to end comparison of outputs) test_neutron_backend_executor contains the rest of the tests. Differential Revision: D77248751
5815e77
to
f01d69f
Compare
Summary: Pull Request resolved: pytorch#11934 The current test_neutron_backend has a hard requirement on tflite due to the Executor comparing the output. Not all systems have tflite, but we would like to have a sanity check on the backend still. To achieve this, this PR splits the existing test into two files test_neutron_backend contains the tests that do not use any Executor logic (ie, no end to end comparison of outputs) test_neutron_backend_executor contains the rest of the tests. Differential Revision: D77248751
LGTM, |
Summary: Pull Request resolved: pytorch#11934 The current test_neutron_backend has a hard requirement on tflite due to the Executor comparing the output. Not all systems have tflite, but we would like to have a sanity check on the backend still. To achieve this, this PR splits the existing test into two files test_neutron_backend contains the tests that do not use any Executor logic (ie, no end to end comparison of outputs) test_neutron_backend_executor contains the rest of the tests. Reviewed By: digantdesai Differential Revision: D77248751
This pull request was exported from Phabricator. Differential Revision: D77248751 |
f01d69f
to
9df4df7
Compare
Summary: The current test_neutron_backend has a hard requirement on tflite due to the Executor comparing the output. Not all systems have tflite, but we would like to have a sanity check on the backend still. To achieve this, this PR splits the existing test into two files test_neutron_backend contains the tests that do not use any Executor logic (ie, no end to end comparison of outputs) test_neutron_backend_executor contains the rest of the tests. Differential Revision: D77248751
Summary:
The current test_neutron_backend has a hard requirement on tflite due to the Executor comparing the output.
Not all systems have tflite, but we would like to have a sanity check on the backend still.
To achieve this, this PR splits the existing test into two files
test_neutron_backend contains the tests that do not use any Executor logic (ie, no end to end comparison of outputs)
test_neutron_backend_executor contains the rest of the tests.
Differential Revision: D77248751