Descriptionuse readable time stamps on log messages.
[Re-opening this because AFAICS a fix for this
has never landed, and currently gocheck always
prints an identical time stamp because the
time calculation overflows.]
On long running tests, I was seeing log output like this:
[LOG] 72.15087 JUJU state: opening state; zookeeper addresses: ["ec2-23-20-157-185.compute-1.amazonaws.com:2181"]
[LOG] 78.46405 JUJU state: waiting for state to be initialized
destroy env
[LOG] 13.73135 JUJU environs/ec2: destroying environment "sample-6326978ae3647455"
This CL makes the time stamp format as a duration
since the start of the test. For instance:
[LOG] 0:00.568 DEBUG juju.environs.tools reading v1.* tools
[LOG] 0:00.569 INFO juju environs/testing: uploading FAKE tools 1.17.3-trusty-amd64
[LOG] 0:00.570 INFO juju environs/testing: uploading FAKE tools 1.17.3-precise-amd64
[LOG] 0:00.571 DEBUG juju.environs.tools no architecture specified when finding tools, looking for any
Note that five tests are currently failing on trunk - this
patch does not fix that - the same tests fail in the same
way.
I have also gofmt'd the files which allow it (all but
printer_test.go).
https://code.launchpad.net/~rogpeppe/gocheck/monotonic-time-stamps/+merge/98841
(do not edit description out of merge proposal)
Patch Set 1 #Patch Set 2 : use readable time stamps on log messages. #Patch Set 3 : use readable time stamps on log messages. #Patch Set 4 : use readable time stamps on log messages. #Patch Set 5 : use readable time stamps on log messages. #Patch Set 6 : use readable time stamps on log messages. #Patch Set 7 : use readable time stamps on log messages. #Patch Set 8 : use readable time stamps on log messages. #Patch Set 9 : use readable time stamps on log messages. #Patch Set 10 : use readable time stamps on log messages. #
MessagesTotal messages: 5
|