You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the other alternative that occurs to me is to add a "report" at the end of the execution that shows a breakdown of how long each task took to run. I think that'd actually be more desirable in my case. The scenario we're having is that we run several tasks in parallel and it's hard to know how long each one is taking due to interleaved output and lack of proper timestamps from the software being invoked
Reacted by Dennis Wielepsky, Tyler, Rick Bowen and Robin Platt
Activity
ivotron commentedon Aug 12, 2021
the other alternative that occurs to me is to add a "report" at the end of the execution that shows a breakdown of how long each task took to run. I think that'd actually be more desirable in my case. The scenario we're having is that we run several tasks in parallel and it's hard to know how long each one is taking due to interleaved output and lack of proper timestamps from the software being invoked
RobinPlatt commentedon Sep 1, 2025
Big +1 for either of these feature ideas (timestamp or report of execution time).
Timestamp seems like the easier of the two as a starting point.
Any particular hold up on these or is it just looking for a community contributor to do it and put in a PR?
trulede commentedon Sep 5, 2025
I might implement something using slog (#2384) which would cover this use case.