Closed Bug 1083671 Opened 10 years ago Closed 10 years ago

Give clobberer an explicit timezone

Categories

(Release Engineering :: General, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: mrrrgn, Unassigned)

Details

Attachments

(2 files)

Clobberer currently uses the system's default timezone on client and server. This could lead to scenarios where clobbers break. The current system should have explicit timezones. Preferably PDT, since that's what everything has been operating up until this point.

*note* verification of PDT as the current clobberer timezone =>

[mphillips@relengwebadm.private.scl3 ~]$ date
Thu Oct 16 00:35:47 PDT 2014
Even though this is a small change, it needs testing on all platforms because it touches the client. This could break clobbers. The only way to test atm is manually, so I'm just throwing this patch out for now and will come back to it with varifications on each platform as I'm able. Let me know if this approach seems lame.
Attachment #8506009 - Flags: feedback?(bugspam.Callek)
Attachment #8506009 - Flags: feedback?(bhearsum)
Nearly forgot always_clobber.php
Comment on attachment 8506009 [details] [diff] [review]
Explicit Timezone For Current Clobberer

Review of attachment 8506009 [details] [diff] [review]:
-----------------------------------------------------------------

Seems fine to me. Yay pytz :)
Attachment #8506009 - Flags: feedback?(bhearsum) → feedback+
Comment on attachment 8506009 [details] [diff] [review]
Explicit Timezone For Current Clobberer

Review of attachment 8506009 [details] [diff] [review]:
-----------------------------------------------------------------

my only concern with this, is if pytz is not available in the context the existing clobberer runs in
Attachment #8506009 - Flags: feedback?(bugspam.Callek) → feedback+
Attachment #8506012 - Flags: feedback+
dustin brought up a good point on here which makes me believe this isn't a top priority for now. Clobberer can still move forward so long as we keep using UNIX epoch time (time.time()) I'll need to investigate if having a TZ environment variable set effects this. If it does, I'll just unset it within the script.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Above, beside "on here," I meant to add this link => https://github.com/mozilla/build-relengapi-clobberer/pull/3#issuecomment-59360424
Component: Tools → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: