remove detailed wandb handler from followup config unit tests

Author: vkakerbeck

tests/unit/graph_learning_test.py

@@ -907,13 +907,16 @@ def test_reproduce_multiple_episodes(self):
         # Check that the arguments for the new experiment are correct
         ###
 
+        # NOTE: detailed wandb logging is currently removed as default. If the handler
+        # is added back, the handler should be removed in unit tests again. (also in the
+        # test_reproduce_single_episode_with_multiple_episode_function)
         # Detailed wandb logging should be automatically built in, though we will remove
         # it to avoid logging tests to wandb
-        self.assertEqual(
-            eval_cfg_2["logging_config"]["wandb_handlers"][-1],
-            DetailedWandbMarkedObsHandler,
-        )
-        eval_cfg_2["logging_config"]["wandb_handlers"].pop()
+        # self.assertEqual(
+        #     eval_cfg_2["logging_config"]["wandb_handlers"][-1],
+        #     DetailedWandbMarkedObsHandler,
+        # )
+        # eval_cfg_2["logging_config"]["wandb_handlers"].pop()
 
         # capsule3DSolid is used as the lone eval object; make sure it is listed once
         # per episode
@@ -1023,14 +1026,6 @@ def test_reproduce_single_episode_with_multiple_episode_function(self):
         # Check that the arguments for the new experiment are correct
         ###
 
-        # Detailed wandb logging should be automatically built in, though we will remove
-        # it to avoid logging tests to wandb
-        self.assertEqual(
-            eval_cfg_2["logging_config"]["wandb_handlers"][-1],
-            DetailedWandbMarkedObsHandler,
-        )
-        eval_cfg_2["logging_config"]["wandb_handlers"].pop()
-
         # check that the object being used is the same one from original exp
         self.assertEqual(
             eval_cfg_1["eval_dataloader_args"].object_names,