On 6/17/19 3:19 PM, Poul-Henning Kamp wrote:
Hi,
Hi Poul-Henning,
For reason now obscured by history, VTest has a (relative) timestamp
on every line of its output:
*** v1 27.4 CLI RX 300
**** v1 27.4 CLI RX|Cannot set the active VCL cold.
** v1 27.4 CLI 300 <vcl.state vcl2 cold>
** top 27.4 === varnish v1 -cliok "vcl.state vcl1 auto"
**** v1 27.4 CLI TX|vcl.state vcl1 auto
*** v1 27.5 CLI RX 200
** v1 27.5 CLI 200 <vcl.state vcl1 auto>
That makes it patently hard to rund diff(1) on VTest outputs.
I want to change this to instead emit separate timestamp lines
whenever the time has changed since the last output to the log:
**** dT 3.864
*** v3 CLI RX 200
**** v3 CLI RX|Child in state running
**** v3 CLI TX|debug.listen_address
**** dT 3.970
*** v3 CLI RX 200
**** v3 CLI RX|/tmp/vtc.49670.11c55d2e/v3.sock -
**** v3 CLI TX|debug.xid 999
**** dT 4.076
**** v3 vsl| 0 CLI - Rd debug.listen_address
Even with the increased precision to milliseconds, the output from
running all the Varnish Cache tests in verbose mode is still 7% smaller
than before.
The Varnish Cache project has OK'ed this, any objections from HAproxy ?
It seems there is no objection ;)
Thank you.
Fred.
