Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 168409 - [Vista] Windows Vista, execution history timestamp is in GMT
Summary: [Vista] Windows Vista, execution history timestamp is in GMT
Status: CLOSED WORKSFORME
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: TPTP (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows Vista
: P2 normal (vote)
Target Milestone: ---   Edit
Assignee: Paul Slauenwhite CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 170550 170551
Blocks: 163254
  Show dependency tree
 
Reported: 2006-12-18 09:49 EST by DuWayne Morris CLA
Modified: 2016-05-05 11:00 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description DuWayne Morris CLA 2006-12-18 09:49:42 EST
Build ID: TPTP4.2.1.1_1127

Steps To Reproduce:
1.  Execute a TPTP URL Test on Windows Vista
2.  Notice that the execution histories in Test Navigator appear with a time expressed in GMT instead of local time.

I think this is bordering on major, because it is a very cumbersome and unpleasant experience for the user to pick the execution results they are interested in when they look at the local time and must figure out what time it is in GMT.


More information:
Comment 1 Mark D Dunn CLA 2006-12-18 12:17:56 EST
Reassign to Bianca. 
Comment 2 Bianca Jiang CLA 2006-12-21 11:38:44 EST
The code is now using the ICU4J function to format the timestamp into a display string based on the default locale. This API returns the time based on current locale on WinXP or 2000 or Linux. Looks like the API doesn't quite work on Vista yet. Need to look for alternative to workaround this. 
Comment 3 Paul Slauenwhite CLA 2006-12-21 11:48:08 EST
(In reply to comment #2)

Thanks Bianca.  In the meantime, can you submit a ICU4J defect (http://bugs.icu-project.org/trac)?
Comment 4 Bianca Jiang CLA 2007-01-04 16:43:56 EST
During my vista testing, the test log viewer can display the time in the current system time zone. 

DuWayne, could you try change the Time Zone on your system from "Date and Time" > Change date and time settings... > Change Time Zone, and see if the test log viewer changes the display of time with the current time zone (I restarted eclipse after changing the system time zone)?
Comment 5 DuWayne Morris CLA 2007-01-05 09:09:58 EST
So, on two Vista machines, I see the same thing, GMT time stamps even though local time is set to Eastern.  Changing the time zone and then changing back to Eastern and re-starting the workbench had no effect.

I noticed the same problem on RPT test logs, so it is not just TPTP.  

It sounded like you were able to make the problem go away somehow that I am unable to reproduce.  By default, it seems the problem will be there for our users.
Comment 6 Paul Slauenwhite CLA 2007-01-15 10:22:46 EST
This is a JVM defect that has been fixed in the IBM JVM 1.5 SR4.
Comment 7 Bianca Jiang CLA 2007-01-15 10:29:48 EST
Deferring to 4.4 as agreed on Test project meeting on Jan. 15 2007.
Comment 8 Paul Slauenwhite CLA 2007-01-15 11:40:38 EST
Since this issue appears to be a JVM defect, this defect will cover both the GMT time stamp found in both the Test Navigator and Test Log View.

Bianca/Duwayne: Do you know if this problem has been found using the Sun JVM?
Comment 9 DuWayne Morris CLA 2007-01-15 13:47:15 EST
According to Earnest, the defect is also in the Sun JVM and notes indicated it is targeted to be fixed in Sun JVM 1.6.

I'm thinking this JVM time stamp issue be noted somewhere in the install notes or release notes for all versions of TPTP on Vista.  The issue will be around for quite some time. 
Comment 10 Paul Slauenwhite CLA 2007-01-15 14:09:11 EST
(In reply to comment #9)

Agreed.  Can you open a Test.Doc defect for the 4.2.2 and 4.3.1 readmes?
Comment 11 Paul Slauenwhite CLA 2007-01-17 09:18:49 EST
Sizing updated as provided by Bianaca.
Comment 12 Paul Slauenwhite CLA 2007-01-26 08:28:37 EST
Targeting to future since cannot be contained in 4.4.
Comment 13 Paul Slauenwhite CLA 2007-01-26 08:33:35 EST
Targeting to future since cannot be contained in 4.4.
Comment 14 Paul Slauenwhite CLA 2007-01-26 08:59:29 EST
As discussed on this week's Test Project call (January 22, 2007), the Test Project will focus on existing P1 - P2/Blocker - Major and P1/Normal and test creation/automation defects (omitting defects dependant on outstanding features) in TPTP 4.4.  All other Test Project defects have been targeted to future.

If this defect has been targeted to future and you/originator feel it should be completed in 4.4, please provide the necessary reason as a reply to this comment or a post to the Test Project mailing list (tptp-test-tooling-dev@eclipse.org).  We will collectively triage and assess our resources to determine a case-by-case decision. 
Comment 15 Paul Slauenwhite CLA 2007-01-26 09:01:07 EST
As discussed on this week's Test Project call (January 22, 2007), the Test Project will focus on existing P1 - P2/Blocker - Major and P1/Normal and test creation/automation defects (omitting defects dependant on outstanding features) in TPTP 4.4.  All other Test Project defects have been targeted to future.

If this defect has been targeted to future and you/originator feel it should be completed in 4.4, please provide the necessary reason as a reply to this comment or a post to the Test Project mailing list (tptp-test-tooling-dev@eclipse.org).  We will collectively triage and assess our resources to determine a case-by-case decision. 
Comment 16 Paul Slauenwhite CLA 2007-01-26 09:03:26 EST
Correction:  The Test Project mailing list is tptp-testing-tools-dev@eclipse.org.
Comment 17 Paul Slauenwhite CLA 2007-11-07 10:18:21 EST
Reassigning to the Project Lead.
Comment 18 Paul Slauenwhite CLA 2008-07-03 09:52:00 EDT
Using the TPTP 4.5.0 GA driver running IBM JRE 1.5 SR4a on Windows Vista Ultimate, the timestamps are rendered in the local time zone but they are ahead by 1 hour.

The Sun JRE 1.5+ needs to be verified for this defect. 
Comment 19 Paul Slauenwhite CLA 2009-06-30 06:54:41 EDT
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. Since this defect is more than 2 years old, it may be no longer relevant. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this defect is resolved as WONTFIX. If this defect is still relevant and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
Comment 20 Paul Slauenwhite CLA 2009-07-02 13:25:31 EDT
Reopening since still relevant.
Comment 21 Ben Chen CLA 2009-07-03 18:13:39 EDT
(In reply to comment #18)
> Using the TPTP 4.5.0 GA driver running IBM JRE 1.5 SR4a on Windows Vista
> Ultimate, the timestamps are rendered in the local time zone but they are ahead
> by 1 hour.
> 
> The Sun JRE 1.5+ needs to be verified for this defect. 
> 

Tried it and it seems the time stamp is consistent with local time zone/time
Comment 22 Paul Slauenwhite CLA 2009-07-06 12:12:39 EDT
(In reply to comment #21)
> (In reply to comment #18)
> > Using the TPTP 4.5.0 GA driver running IBM JRE 1.5 SR4a on Windows Vista
> > Ultimate, the timestamps are rendered in the local time zone but they are ahead
> > by 1 hour.
> > 
> > The Sun JRE 1.5+ needs to be verified for this defect. 
> > 
> 
> Tried it and it seems the time stamp is consistent with local time zone/time
> 

Ben has confirmed that this problem is now fixed with both the Sun and IBM 1.6 JREs using the TPTP 4.6 GA driver.
Comment 23 Paul Slauenwhite CLA 2010-05-17 08:16:40 EDT
Originator's email is invalid.  

Closing.