Rename the DEBUG logging level to DEBUGGING.

Some software projects compile C/C++ code with -DDEBUG (equivalent to
-DDEBUG=1) in debug builds. Notably, this is done by default in debug builds on iOS. Therefore, we should avoid using DEBUG as an identifier in C/C++ code.
Change: 146840049

Author: tensorflower-gardener

tensorflow/core/util/event.proto

@@ -43,7 +43,11 @@ message Event {
 message LogMessage {
   enum Level {
     UNKNOWN = 0;
-    DEBUG = 10;
+    // Note: The logging level 10 cannot be named DEBUG. Some software
+    // projects compile their C/C++ code with -DDEBUG in debug builds. So the
+    // C++ code generated from this file should not have an identifier named
+    // DEBUG.
+    DEBUGGING = 10;
     INFO = 20;
     WARN = 30;
     ERROR = 40;

tensorflow/python/training/tensorboard_logging.py

@@ -56,7 +56,7 @@
 # Map from the tensorboard_logging logging enum values to the proto's enum
 # values.
 _LEVEL_PROTO_MAP = {
-    DEBUG: event_pb2.LogMessage.DEBUG,
+    DEBUG: event_pb2.LogMessage.DEBUGGING,
     INFO: event_pb2.LogMessage.INFO,
     WARN: event_pb2.LogMessage.WARN,
     ERROR: event_pb2.LogMessage.ERROR,

tensorflow/python/training/tensorboard_logging_test.py

@@ -94,7 +94,7 @@ def testVerbosity(self):
     tensorboard_logging.debug("debug")
 
     self.assertLoggedMessagesAre([(event_pb2.LogMessage.ERROR, "error"),
-                                  (event_pb2.LogMessage.DEBUG, "debug")])
+                                  (event_pb2.LogMessage.DEBUGGING, "debug")])
     # All message should be logged because tensorboard_logging verbosity doesn't
     # affect logging verbosity.
     self.assertEqual(3, self.logged_message_count)