New issue
Advanced search Search tips

Issue 671629 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 714599
Owner: ----
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Swarming pending time is incorrect??

Project Member Reported by martiniss@chromium.org, Dec 6 2016

Issue description

https://chromium-swarm.appspot.com/task?id=32ecaf76696eb510&refresh=10&show_raw=1 is the bad link.

From what I can tell, it got triggered at "12/6/2016, 3:21:26 AM (EST)", and it's 10:31 EST right now. The expiry time on the task page says it should expire at "12/6/2016, 9:21:26 AM (EST)", but it hasn't expired....

Screenshot in case the task changes: https://screenshot.googleplex.com/UMYegFYcc71
 
And now, when I refresh the page, it's showing the expiry time as 12:21 PM EST?  Sounds like a time zone bug...
Cc: kjlubick@chromium.org
https://screenshot.googleplex.com/PiZAYD6feKm

As far as I can tell from my own view, the UI is reporting the right data. It would have been helpful to take a screenshot. Maybe there's a bug in the timezone calculation for UI?
The UI uses the browser toLocaleDateString() so it's not doing any math I'm aware of.

If you see this again, would you be able to mouseover the incorrect time?  It will show you the raw GMT string if you do that.
I saw the same thing on https://chromium-swarm.appspot.com/task?id=32ecb084ef639810&refresh=10&show_raw=1. I moused over the started time, which said "12/6/2016, 7:27:22 AM (EST)", and the mouse over text said "Tue Dec 06 2016 10:27:22 GMT -0500 (EST)" (manually transcribed that, so not exactly that, but close to it).
Strange.  Something is funky there.  What time zone are you actually in? EST?
I'm in EST right now, yes.
Hmm... I tried fiddling with the timezone of my computer and could not trigger this behavior.  

All timestamps are received like:

"created_ts": "2016-12-06T11:21:26.885690"

and parsed like:

var d = new Date(time);

and the text you see on screen is made like:

var str = d.toString();
var timezone = str.substring(str.indexOf("("));
return d.toLocaleString() + " " + timezone;

My only thought is that new Date() doesn't get the parsing right because it still has to guess what timezone it is given data in.  It defaults to UTC, but maybe I should specify the timezone just to be sure.

Comment 8 by kjlubick@google.com, May 11 2017

Mergedinto: 714599
Status: Duplicate (was: Available)
It turns out, there was some timezone bug in the UI.  This should be fixed now, haven't seen it since.

Sign in to add a comment