You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.
Running regression test for OpPerf entails
a. Updating the operator (API change) shouldn't break OpPerf utility
b. API changes should be flagged by OpPerf
c. Integration of OpPerf in CI/Dashboard (detailed discussion in existing open issue #15757 by @sandeep-krishnamurthy )
Motivation
Given that we are adding so many new op coverage thanks to your hard work, should we add regression tests to make sure the existing ops are not being negatively affected?
Description
Running regression test for OpPerf entails
a. Updating the operator (API change) shouldn't break OpPerf utility
b. API changes should be flagged by OpPerf
c. Integration of OpPerf in CI/Dashboard (detailed discussion in existing open issue #15757 by @sandeep-krishnamurthy )
Motivation
Thanks to @apeforest
#16253 (review)
Discussion in PR #16253
The text was updated successfully, but these errors were encountered: