Fixing test breakages caused by newer versions of our dependencies.

- example_proto_coder_test: default implementation uses 'python' proto mode. We were previously relying on the fact that some of our dependencies set the proto implementation mode to 'cpp' (by checking it against the default value of `proto_implementation_type` flag). This change explicitly sets the implementation mode to 'cpp' for the test.

- impl_test: beam's error msg is slightly different in newer version (of apache-beam?) ("list" vs "<class 'list'>"), so I generalized it.

PiperOrigin-RevId: 474419283

Author: iindyk

tensorflow_transform/beam/impl_test.py

@@ -4316,9 +4316,9 @@ def testHandleBatchError(self):
     def preprocessing_fn(inputs):
       return {'x_scaled': tft.scale_to_0_1(inputs['x'])}
 
-    # Exception type depends on the running being used.
+    # Exception type depends on the runner being used.
     with self.assertRaisesRegexp(
-        (RuntimeError, ValueError, TypeError), 'has type list'):
+        (RuntimeError, ValueError, TypeError), 'has type .*list'):
       # TODO(b/149997088): Remove this explicit use of DirectRunner.
       with beam.Pipeline() as pipeline:
         metadata = tft.DatasetMetadata.from_feature_spec({

tensorflow_transform/coders/example_proto_coder_test.py

@@ -24,10 +24,9 @@
 # pretty early on.
 if any(arg == '--proto_implementation_type=python' for arg in sys.argv):
   os.environ['PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION'] = 'python'
-elif any(arg == '--proto_implementation_type=cpp' for arg in sys.argv):
+else:
   os.environ['PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION'] = 'cpp'
-elif any(arg.startswith('--proto_implementation_type') for arg in sys.argv):
-  raise ValueError('Unexpected value for --proto_implementation_type')
+  os.environ['PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION_VERSION'] = '2'
 
 # pylint: disable=g-import-not-at-top
 import numpy as np