| commit | b451812551ad4e2be7ea001865d02e0497430afd | |
| author | Lucian Wischik <ljw@fb.com> | |
| Thu, 21 May 2020 10:12:47 +0000 (21 03:12 -0700) | ||
| committer | Facebook GitHub Bot <facebook-github-bot@users.noreply.github.com> | |
| Thu, 21 May 2020 10:19:45 +0000 (21 03:19 -0700) | ||
| tree | ddad9ac34b3991c3c92a64f51783393acbc7bcf1 | treesnapshot (tar.gz zip) |
| parent | 59c4d453197a7f19935994e35f7be7a8485dcf38 | commitdiff |
record start+end times of hh invocations
Summary:
I'm investigating a rage report. I'm puzzled by the timings shown in the server logs. I'd like to get a timestamp for when `hh rage` invokes two subsidiary invocations of hh (one for server-state, one to get errors). That's what this diff provides.
Other system-wide changes rolled in:
1. I augmented `Process_success.t` and `Process_failure.t` to keep a record of start+end times.
2. I consolidated all "float->timestring" conversions into a single central Utils.timestring function. (previously it existed in Hh_logger and typing_service_state_utils)
Reviewed By: arxanas
Differential Revision: D21672405
fbshipit-source-id: f1400aa444c735ba930e182702585cffcaa7917a
Summary:
I'm investigating a rage report. I'm puzzled by the timings shown in the server logs. I'd like to get a timestamp for when `hh rage` invokes two subsidiary invocations of hh (one for server-state, one to get errors). That's what this diff provides.
Other system-wide changes rolled in:
1. I augmented `Process_success.t` and `Process_failure.t` to keep a record of start+end times.
2. I consolidated all "float->timestring" conversions into a single central Utils.timestring function. (previously it existed in Hh_logger and typing_service_state_utils)
Reviewed By: arxanas
Differential Revision: D21672405
fbshipit-source-id: f1400aa444c735ba930e182702585cffcaa7917a