Closed Bug 619728 Opened 14 years ago Closed 5 years ago

Messages sent via the python shim lib assume Pacific

Categories

(Webtools :: Pulse, defect, P4)

defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: christian, Unassigned)

Details

Attachments

(3 obsolete files)

Messages sent via the python shim lib assume Pacific. This isn't the case for releng machines, so "sent" times are in the future. Also, I think pulse is in phoenix (though I have it set to Pacific).
Attachment #500907 - Flags: review?(clegnitto)
Please ignore, testing something else
Attachment #500914 - Flags: review?(clegnitto)
Please ignore, testing something else, part 2
Attachment #500914 - Attachment is obsolete: true
Attachment #500914 - Flags: review?(clegnitto)
Attachment #500916 - Flags: review?(clegnitto)
Please ignore, testing something else, part 3
Attachment #500916 - Attachment is obsolete: true
Attachment #500916 - Flags: review?(clegnitto)
Attachment #500907 - Flags: review?(clegnitto)
Attachment #500907 - Attachment is obsolete: true
I assume this is referring to buildbot messages specifically.  Not sure if this remains an issue or not.
Summary: Messages sent via the python shim lib assume Pacific → Messages sent via the buildbot shim lib assume Pacific
Rereading, I guess this was actually an assumption across all shims, of which there were more at the time.  Atm the only other active publisher is SimpleBugzilla, and its timestamps are in UTC, so the new summary still stands.

The solution is either switching all buildbot messages to Pacific (which maybe they are now) or all of them to UTC.  I prefer the latter, but I find the ambiguity of DST switches (to ST in particular, since an hour is repeated) when no full timezone is provided to be frustrating and hard to fix.
Assignee: christian → nobody
Summary: Messages sent via the buildbot shim lib assume Pacific → Messages sent via the python shim lib assume Pacific
Priority: -- → P4

Buildbot had the odd habit of doing things in pacific time. So I think this is solved.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: