[Pipelining]

Minor logging fix

It does make the logging wider but its better than having the lines
interspersed with unrelated lines due to mixed use of print and logging.

[ghstack-poisoned]

torch/distributed/pipelining/schedules.py

@@ -2216,9 +2216,7 @@ BACKWARD_INPUT, BACKWARD_WEIGHT, and OVERLAP_F_B are supported."
                     time_step,
                     action,
                 )
-                # TODO(whc) what is the best practice for printing a multiline log?
-                # logger will split it into multiple log lines, but this makes it hard to read (too wide)
-                print(
+                logger.error(
                     _format_pipeline_order(
                         self.pipeline_order_with_comms,  # type: ignore[arg-type]
                         error_step_number=time_step,