Bug 31391

Summary: SVNTest.test_svn_apply may fail in different timezone
Product: WebKit Reporter: Shinichiro Hamaji <hamaji>
Component: Tools / TestsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: eric, mithro
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
Attachments:
Description Flags
Patch v1 eric: review-

Shinichiro Hamaji
Reported 2009-11-11 20:27:23 PST
svn-apply sets TZ=PST8PDT but SVNTest.test_svn_apply doesn't change this. This can cause unittest failure.
Attachments
Patch v1 (1.30 KB, patch)
2009-11-11 20:28 PST, Shinichiro Hamaji
eric: review-
Shinichiro Hamaji
Comment 1 2009-11-11 20:28:14 PST
Created attachment 43028 [details] Patch v1
Eric Seidel (no email)
Comment 2 2009-11-13 13:43:32 PST
Comment on attachment 43028 [details] Patch v1 Isn't there a cleaner fix w/o using os.environ? I would think Date would have some sort of timezone adjustment methods...
Shinichiro Hamaji
Comment 3 2009-11-16 02:41:20 PST
If nothing changed after I did similar stuff with Python (and as far as I searched webs now), I think there are no easy way to do this. If I understand correctly, Python provides a framework to convert datetime object among different timezones, but it doesn't provide information of actual timezones. Like following blog post, we need to provide information of each timezone by ourselves. http://uswaretech.com/blog/2009/02/understanding-datetime-tzinfo-timedelta-timezone-conversions-python/ There seems to be a library which provides information of timezones, but it seems not to be the standard library. http://pytz.sourceforge.net/ I think my patch would be OK as prepare-ChangeLog is doing the same thing after all and it's just a test. Another idea to fix this is adding an --date flag into prepare-ChangeLog and use this flag in this unittest. If you prefer this approach, I'll do the fix. Of course, if I'm missing something and there is a better way, I'd like to use the way.
Tim 'mithro' Ansell
Comment 4 2013-01-21 19:36:15 PST
This bug was fixed by jochen@chromium.org in r93257 http://trac.webkit.org/changeset/93257 *** This bug has been marked as a duplicate of bug 65877 ***
Note You need to log in before you can comment on or make changes to this bug.