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
For making sense of the debug output it could be helpful to have each line prefixed with a timestamp when the output was generated. Maybe something like ping's -D option (" -D: Print timestamp (unix time + microseconds as in gettimeofday) before each line.") or the same offset by the tests starting time?
The text was updated successfully, but these errors were encountered:
On Fri, May 6, 2022 at 3:18 AM moeller0 ***@***.***> wrote:
For making sense of the debug output it could be helpful to have each line
prefixed with a timestamp when the output was generated. Maybe something
like ping's -D option (" -D: Print timestamp (unix time + microseconds as
in gettimeofday) before each line.") or the same offset by the tests
starting time?
—
Reply to this email directly, view it on GitHub
<#17>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACCP2CURCXOEWM4RZ5HEPMTVITBT7ANCNFSM5VHIOSGQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
For making sense of the debug output it could be helpful to have each line prefixed with a timestamp when the output was generated. Maybe something like ping's -D option (" -D: Print timestamp (unix time + microseconds as in gettimeofday) before each line.") or the same offset by the tests starting time?
The text was updated successfully, but these errors were encountered: