Fix line-too-long CodeFactor warning

frontend/test/pytest/test_callback.py

@@ -233,10 +233,11 @@ def identity(arg) -> int:
     def cir(x):
         return identity(x)
 
-    # NOTE: Currently, this will raise a TypeError exception on Linux and the same exception wrapped
-    # as a RuntimeError on macOS. This appears to be related to using nanobind for the Python/C++
-    # bindings. To avoid separate test cases for Linux and macOS, we accept either exception type
-    # here and match on the string below, which should be contained in the messages of both.
+    # NOTE: Currently, this will raise a TypeError exception on Linux and the same exception
+    # wrapped as a RuntimeError on macOS. This appears to be related to using nanobind for the
+    # Python/C++ bindings. To avoid separate test cases for Linux and macOS, we accept either
+    # exception type here and match on the string below, which should be contained in the messages
+    # of both.
     # TODO: Why does this happen?
     with pytest.raises((TypeError, RuntimeError), match="Callback identity expected type"):
         cir(arg)
@@ -339,10 +340,11 @@ def cir(x):
     captured = capsys.readouterr()
     assert captured.out.strip() == ""
 
-    # NOTE: Currently, this will raise a ValueError exception on Linux and the same exception wrapped
-    # as a RuntimeError on macOS. This appears to be related to using nanobind for the Python/C++
-    # bindings. To avoid separate test cases for Linux and macOS, we accept either exception type
-    # here and match on the string below, which should be contained in the messages of both.
+    # NOTE: Currently, this will raise a ValueError exception on Linux and the same exception
+    # wrapped as a RuntimeError on macOS. This appears to be related to using nanobind for the
+    # Python/C++ bindings. To avoid separate test cases for Linux and macOS, we accept either
+    # exception type here and match on the string below, which should be contained in the messages
+    # of both.
     # TODO: Why does this happen?
     with pytest.raises(
         (ValueError, RuntimeError), match="debug.callback is expected to return None"
@@ -965,10 +967,11 @@ def result(x):
         return jnp.sum(some_func(jnp.sin(x)))
 
     x = 0.435
-    # NOTE: Currently, this will raise a TypeError exception on Linux and the same exception wrapped
-    # as a RuntimeError on macOS. This appears to be related to using nanobind for the Python/C++
-    # bindings. To avoid separate test cases for Linux and macOS, we accept either exception type
-    # here and match on the string below, which should be contained in the messages of both.
+    # NOTE: Currently, this will raise a TypeError exception on Linux and the same exception
+    # wrapped as a RuntimeError on macOS. This appears to be related to using nanobind for the
+    # Python/C++ bindings. To avoid separate test cases for Linux and macOS, we accept either
+    # exception type here and match on the string below, which should be contained in the messages
+    # of both.
     # TODO: Why does this happen?
     with pytest.raises((TypeError, RuntimeError), match="Callback some_func expected type"):
         result(x)