@@ -324,17 +324,9 @@ macro_rules! define_run_body {
324
324
let mut have_decayed_scorer = false ;
325
325
326
326
loop {
327
- log_trace!( $logger, "Processing ChannelManager events..." ) ;
328
327
$process_channel_manager_events;
329
- log_trace!( $logger, "Done processing ChannelManager events." ) ;
330
-
331
- log_trace!( $logger, "Processing ChainMonitor events..." ) ;
332
328
$process_chain_monitor_events;
333
- log_trace!( $logger, "Done processing ChainMonitor events." ) ;
334
-
335
- log_trace!( $logger, "Processing OnionMessageHandler events..." ) ;
336
329
$process_onion_message_handler_events;
337
- log_trace!( $logger, "Done processing OnionMessageHandler events." ) ;
338
330
339
331
// Note that the PeerManager::process_events may block on ChannelManager's locks,
340
332
// hence it comes last here. When the ChannelManager finishes whatever it's doing,
@@ -347,9 +339,7 @@ macro_rules! define_run_body {
347
339
// ChannelManager, we want to minimize methods blocking on a ChannelManager
348
340
// generally, and as a fallback place such blocking only immediately before
349
341
// persistence.
350
- log_trace!( $logger, "Processing PeerManager events..." ) ;
351
342
$peer_manager. as_ref( ) . process_events( ) ;
352
- log_trace!( $logger, "Done processing PeerManager events." ) ;
353
343
354
344
// Exit the loop if the background processor was requested to stop.
355
345
if $loop_exit_check {
0 commit comments