We are starting to require newer versions of tflite as part of running some of the models that we have . Further we are also noticing a whole bunch of tests especially for SPLIT, unpack and others that need special handling in the testsuite for tflite versions as tflite 1.13 is buggy in the way it creates models for Split and unpack. A lot of our tests are written in a way that runs the same tests in both the original framework and via TVM. However we’ve seen atleast 2 operators (SPLIT and UNPACK) that are broken when creating the models using the tflite converter ?
Does anyone else in the community have any experience with moving up to 1.15.0 in our CI system for Tensorflow and TFlite so that the newer operators are supported and bugs are fixed with respect to creating models ? I’ve been slowly working through a bunch of failures , however I wanted to check in on this with the community before spending more time on it.
Further we need to think about the following wider topics.
Tensorflow 2.0 and TFlite 2.0 - how do we plan to support these ? It sounds to me like TF 2.0 is substantially different from TF 1.x that we need 2 different strands of activity and potentially another strand of CI testing.
While we are here, we should look to get to a general pragmatic policy around upgrades to the relevant networks. For eg. questions to answer are whether the last stable version is good enough everywhere as we need to be able to handle recent enough operators and we potentially need to think about upgrades regularly ?