Fixing the tests which were failing due to exception wording change.

Signed-off-by: cuneyt.ozdas <cuneyt.ozdas@autodesk.com>

Author: cozdas

tests/cpu/ColorSpace_tests.cpp

@@ -1866,11 +1866,11 @@ OCIO_ADD_TEST(ColorSpace, interop_id)
     // Test invalid InteropID with non-ASCII characters.
     const char * invalidNonASCII1 = "café_scene";  // Contains é (0xC3 0xA9)
     OCIO_CHECK_THROW_WHAT(cs->setInteropID(invalidNonASCII1), OCIO::Exception,
-                          "contains non-ASCII characters");
+                          "is invalid: only ASCII characters [0x00..0x7F] are allowed.");
 
     const char * invalidNonASCII2 = "space±_name";  // Contains ± (ANSI 0xB1)
     OCIO_CHECK_THROW_WHAT(cs->setInteropID(invalidNonASCII2), OCIO::Exception,
-                          "contains non-ASCII characters");
+                          "is invalid: only ASCII characters [0x00..0x7F] are allowed.");
 }
 
 OCIO_ADD_TEST(ColorSpace, interop_id_serialization)

tests/python/ColorSpaceTest.py

@@ -693,11 +693,11 @@ def test_interop_id(self):
         # Test invalid InteropID with non-ASCII characters.
         with self.assertRaises(Exception) as context:
             self.colorspace.setInteropID('café_scene')  # Contains é (UTF-8)
-        self.assertIn("contains non-ASCII characters", str(context.exception))
+        self.assertIn("is invalid: only ASCII characters [0x00..0x7F] are allowed.", str(context.exception))
 
         with self.assertRaises(Exception) as context:
             self.colorspace.setInteropID('space±_name')  # Contains ± (ANSI 0xB1)
-        self.assertIn("contains non-ASCII characters", str(context.exception))
+        self.assertIn("is invalid: only ASCII characters [0x00..0x7F] are allowed.", str(context.exception))
 
     def test_amf_transform_ids(self):
         """