Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 18678 invoked by uid 500); 21 May 2002 04:25:29 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 18660 invoked from network); 21 May 2002 04:25:29 -0000 Date: Mon, 20 May 2002 21:25:20 -0700 From: Jon Travis To: "William A. Rowe, Jr." Cc: dev@apr.apache.org Subject: Re: APR time test failing Message-ID: <20020520212520.A19887@covalent.net> References: <20020520194724.A17946@covalent.net> <20020520194724.A17946@covalent.net> <20020520195106.A18038@covalent.net> <5.1.0.14.2.20020520231508.0207cdf8@pop3.rowe-clan.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <5.1.0.14.2.20020520231508.0207cdf8@pop3.rowe-clan.net>; from wrowe@rowe-clan.net on Mon, May 20, 2002 at 11:17:49PM -0500 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Mon, May 20, 2002 at 11:17:49PM -0500, William A. Rowe, Jr. wrote: > At 09:51 PM 5/20/2002, Jon Travis wrote: > >On Mon, May 20, 2002 at 07:47:24PM -0700, Jon Travis wrote: > > > My time test is failing. I get a mismatch: > > > > > > checking localtime explode == GMT implode mismatch > > > apr_now() 1021948993979908 > > > apr_implode() returned 1021981393979908 > > > error delta was 32400000000 > > > should have been 0 > > > >Sorry, should have been more thorough. > > > >This problem only occurs under Windows for me. Under UNIX the test > >works fine. > > 9 hour delta... evidently we missed timezone data, and then MIS > compensated for the DST delta [otherwise, where would 9hrs -> PST > come from... PDT should be 7hrs from GMT, no?] Yeah, it's an interesting one -- apr_time_now() should be GMT though, and not have anything to do with timezones (not saying they aren't playing a part in this issue, though). This problem manifested itself when a program I was running on Windows had a hard time communicating with a program under UNIX. Both used apr_time_now() to determine the current time, and I guess they came up with different answers. -- Jon