You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 5, 2018. It is now read-only.
when starting a machine, it immediately starts with a start time two hours behind the actual StartTime. Consequently, the consumed wall clock time is two hours longer than the actual time. I have a feeling that the time zone is accounted for twice. Need to check.
Consider the excerpt of the record below. A start time of 1379483403 actually translates to "Wed Sep 18 05:50:03 UTC 2013". However, the machine was started at "Wed Sep 18 09:50:03 CEST 2013", which would translate to "Wed Sep 18 07:50:03 UTC 2013".
I will have a look at the code to see if I can find the cause.
Hi,
when starting a machine, it immediately starts with a start time two hours behind the actual StartTime. Consequently, the consumed wall clock time is two hours longer than the actual time. I have a feeling that the time zone is accounted for twice. Need to check.
Consider the excerpt of the record below. A start time of 1379483403 actually translates to "Wed Sep 18 05:50:03 UTC 2013". However, the machine was started at "Wed Sep 18 09:50:03 CEST 2013", which would translate to "Wed Sep 18 07:50:03 UTC 2013".
I will have a look at the code to see if I can find the cause.
Best regards,
Björn
"8ffd6105-9b7a-40fe-9a99-223fbc60dcf8" : {
"WallDuration" : 8700,
[...]
"Status" : "started",
[...]
"StartTime" : "1379483403",
[...]
},
The text was updated successfully, but these errors were encountered: