Hi,
I had forgotten the details how timestamps are generated. After a
little digging I learned that you are right, timestamps in logs are
always shown in the local timezone regardless the timezone of the
machine where tests were executed. This is summary of how timestamps
shown in logs/reports are generated:
1. When generating log files, timestamps are written as seconds since
the Unic epoch. This value is the same at the same time regardless the
timezone.
2. Time stamp actually shown in logs/reports is generated based on the
epoch time using Javascript Date object. This object always shows time
in the local time.
If we wanted to show log messages using the original timezone, we
needed to create Javascript Date objects somehow taking the original
timezone into account. It would be easy to store timezone information
in the generated log files, but we needed to store it also in the
output.xml files to allow generating logs/reports later. Also needed
to take into account having different timezones when combining
results. Finally, needed to decide do we want to always show
timestamps using the original timezone (changes behavior) or should
that be configurable.
All of the above ought to be doable but requires some actual work. As
the first step you could submit an issue, but seeing this implemented
in the near future is likely to require some help in form of a pull
request.
Cheers,
.peke
>> > email to
robotframework-u...@googlegroups.com.
> --
> You received this message because you are subscribed to the Google Groups
> "robotframework-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
robotframework-u...@googlegroups.com.