From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: "ago" times on buildfarm status page |
Date: | 2019-08-21 15:10:04 |
Message-ID: | cc088eb1-a9fa-095b-a3ae-f578ce5396c6@2ndQuadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 8/21/19 3:40 AM, Peter Eisentraut wrote:
> I find the time displays like
>
> 01:03 ago
>
> on the buildfarm status page unhelpful.
>
> First, I can never tell whether this is hours-minutes or minutes-seconds
> -- there is probably a less ambiguous format available.
This is hours:minutes. days are always explicitly prepended if greater
than 0.
>
> But more importantly, the page doesn't say when it was generated, so a
> relative time like this is meaningless. The page might have most
> recently reloaded last night. That means when I look at the page, I
> *always* have to reload it first to make sense of the times.
>
> I notice that the page source actually includes absolute times that are
> then converted to relative using some JavaScript. Could we perhaps just
> turn that off? Or preferably convert to local time. I can much easier
> make sense of an absolute local time: I can compare that to the clock in
> the corner of the screen, and I can compare that, say, to a commit
> timestamp.
>
Maybe.
TBH the whole buildfarm UI is rather dated and clunky. But it needs work
from a web monkey, which I am really not.
cheers
andrew
--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2019-08-21 15:18:58 | Re: [HACKERS] [PATCH] pageinspect function to decode infomasks |
Previous Message | Andrew Dunstan | 2019-08-21 15:07:02 | Re: "ago" times on buildfarm status page |