Timestamps in Chromium logs

[Antonis Tsakiridis]

Hello, 

I'm doing some webrtc test scenarios targeting headless chromium (using xvfb). The problem is that the log entries are of this form:

[40809:1295:0317/153829:INFO:CONSOLE(4299)] "WebRTCommCall:onRtcPeerConnectionIceChangeEvent(): this.peerConnection.iceGatheringState=complete", source: http://127.0.0.1:10510/scripts/WebRTComm.js (4299)

and I can't figure out what is going on as there is no timestamp in the logs. Is there a way to enable timestamps from the command line? Cause I haven't been able to find any (in non headless mode I can add timestamp in the Developer Tools but in headless this is not an option)

I read on the net that there's an indication of 'ticks' that as supposed to measure time somehow? But the only variable number above is 153829 and that doesn't seem to have the period of a second. It would also help me if there's a resource somewhere the documents what all those fields are in each of the log lines

Best regards,

Antonis Tsakiridis

[Christian Biesinger]

The timestamp is there -- 0317/153829. Is March 17 at 15:38:29.

-Christian

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

[Antonis Tsakiridis]

I feel embarrassed :(

Thanks a lot, do you think if there's a way to also show milliseconds?

Best regards,

Antonis

--

Antonis Tsakiridis

Lead Developer, Mobile SDKs at TeleStax

antonis.t...@telestax.com

http://www.telestax.com

[Christian Biesinger]

Looks like that's not possible:
https://code.google.com/p/chromium/codesearch#chromium/src/base/logging.cc&sq=package:chromium&type=cs&l=762

There may be a way to enable the tick count (...reading more...) ah,
apparently on Windows the tick count is milliseconds. On Linux it's
microseconds and I can't figure out what it is on Mac.

But on Chrome we turn it off:
https://code.google.com/p/chromium/codesearch#chromium/src/chrome/common/logging_chrome.cc&sq=package:chromium&type=cs&l=324&rcl=1458487987

sorry!

Also, for reference, the first two fields are process ID and thread
ID, respectively.

-Christian

[Antonis Tsakiridis]

Great thanks a lot for the details!