On Thu, Mar 24, 2022 at 1:50 PM Victor Toso <victort...@redhat.com> wrote:
>
> Signed-off-by: Victor Toso <victort...@redhat.com>
> ---
> qapi/run-state.json | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/qapi/run-state.json b/qapi/run-state.json
> index 1b9f64c9cd..f87b9378ac 100644
> --- a/qapi/run-state.json
> +++ b/qapi/run-state.json
> @@ -426,7 +426,8 @@
> # Example:
> #
> # <- { "event": "GUEST_PANICKED",
> -# "data": { "action": "pause" } }
> +# "data": { "action": "pause" },
> +# "timestamp": { "seconds": 1267061043, "microseconds": 959568 } }
> #
> ##
> { 'event': 'GUEST_PANICKED',
> @@ -446,7 +447,8 @@
> # Example:
> #
> # <- { "event": "GUEST_CRASHLOADED",
> -# "data": { "action": "run" } }
> +# "data": { "action": "run" },
> +# "timestamp": { "seconds": 1267061043, "microseconds": 959568 } }
> #
> ##
> { 'event': 'GUEST_CRASHLOADED',
> --
> 2.35.1
>
Someone once reviewed my documentation and noted that the timestamps
were correctly chronological.
... I feel like I have been *hurt* somehow.
Anyway:
Reviewed-by: John Snow <js...@redhat.com>
