Remove reference consistency tests #8023
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reiterating from #8013 (comment):
We have consistency tests against v1 as part of our regular v2 tests. Meaning, the only things left in here are transforms that are not part of v1. These are the transforms that are part of our reference scripts and became part of the v2 API. The tests for them are
vision/test/test_transforms_v2_consistency.py
Line 37 in 67f3ce2
vision/test/test_transforms_v2_consistency.py
Line 142 in 67f3ce2
As for all the other consistency tests, these tests had the most value during the heavy development to avoid breaking consistency. Now that the API is stable and we need to keep BC anyway and the tests have been running smoothly for almost a year, their value is fairly low.
Plus, #7724 and the sister PRs enabled the v2 transforms in the references. In the long term, we'll likely drop support for transforms v1 in the reference scripts.
My vote is out for removing them completely hence this PR.
cc @vfdev-5