blueprint icon indicating copy to clipboard operation
blueprint copied to clipboard

[TASK] Stop spamming in Tangle tests while waiting for job results

Open Serial-ATA opened this issue 9 months ago • 0 comments

Overview

In a Tangle job, the following is printed in a loop for every block while waiting for a result:

 INFO gadget_tangle_testing_utils::node::transactions: Waiting for job completion. Found 0 results ... service_id=0 call_id=0 required_count=1 count=0
 INFO gadget_tangle_testing_utils::node::transactions: Waiting for job completion. Found 0 results ... service_id=0 call_id=0 required_count=1 count=0
 INFO gadget_tangle_testing_utils::node::transactions: Waiting for job completion. Found 0 results ... service_id=0 call_id=0 required_count=1 count=0
 INFO gadget_tangle_testing_utils::node::transactions: Waiting for job completion. Found 0 results ... service_id=0 call_id=0 required_count=1 count=0
 INFO gadget_tangle_testing_utils::node::transactions: Waiting for job completion. Found 0 results ... service_id=0 call_id=0 required_count=1 count=0
 INFO gadget_tangle_testing_utils::node::transactions: Waiting for job completion. Found 0 results ... service_id=0 call_id=0 required_count=1 count=0
 INFO gadget_tangle_testing_utils::node::transactions: Waiting for job completion. Found 0 results ... service_id=0 call_id=0 required_count=1 count=0
...

This is annoying for slow jobs, where other logs may be buried by this.

We should probably space it out, either:

  • Printing it out once to inform the user that we're now looking for a result, and then warning them after awhile that nothing was found. This would be similar to how a warning is printed if a test has been running for >60sec with the default Rust test harness
  • Just print it periodically, after every N blocks

Serial-ATA avatar Mar 13 '25 20:03 Serial-ATA