Skip Menu |
 

This queue is for tickets about the DBIx-Class-TimeStamp CPAN distribution.

Report information
The Basics
Id: 48385
Status: open
Priority: 0/
Queue: DBIx-Class-TimeStamp

People
Owner: Nobody in particular
Requestors: kmx [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Failing tests t/06timestamp.t and t/07date.t
Hi, I have experienced the following failures during test while trying to install DBIx-Class-TimeStamp-0.12 t/05datetime.t ..... ok # Failed test 'update and create timestamp' # at t/06timestamp.t line 28. # got: '2009-08-02T22:45:56' # expected: '2009-08-02T22:45:55' # Looks like you failed 1 test of 3. t/06timestamp.t .... # Failed test 'update and create timestamp' # at t/07date.t line 28. # got: '2009-08-02T22:45:58' # expected: '2009-08-02T22:45:57' # Looks like you failed 1 test of 3. My perl - win32 strawbarry perl 5.8.9; however it does not seem to be a win32 specific issue. As you can see it is a sort of timing problem and does not happen always. I think that with current implementation you cannot assume update and create timestamps to be exactly the same. Changing tests in the following way could solve this issue: -is $row->t_updated, $row->t_created, 'update and create timestamp'; +cmp_ok($row->t_updated, '>=', $row->t_created, 'update and create timestamp'); -- kmx
Download (untitled) / with headers
text/plain 359b
Hi, can I somehow help with getting a fix for the issue discussed in this RT into official release? If you give me a feedback whether you prefer to patch the test (not testing createtime==updatetime but createtime<=updatetime) or to patch the module to assure the createtime to be exactly the same value as updatetime - I can try to prepare a patch. -- kmx
Download (untitled) / with headers
text/plain 695b
On Fri Aug 14 09:48:38 2009, KMX wrote: Show quoted text
> Hi, > > can I somehow help with getting a fix for the issue discussed in this RT > into official release? > > If you give me a feedback whether you prefer to patch the test (not > testing createtime==updatetime but createtime<=updatetime) or to patch > the module to assure the createtime to be exactly the same value as > updatetime - I can try to prepare a patch. > > -- > kmx
Honestly the only thing I can think of is to either 1) rewrite the tests so that all these bits don't need to be equal or 2) skip the tests in cases where the fine grained time module is not present. 1 Is probably the only way we are going to fix it for certain. john
Subject: Re: [rt.cpan.org #48385] Failing tests t/06timestamp.t and t/07date.t
Date: Mon, 17 Aug 2009 15:52:24 +0200
To: John Napiorkowski via RT <bug-DBIx-Class-TimeStamp [...] rt.cpan.org>
From: Florian Ragwitz <rafl [...] debian.org>
Download (untitled) / with headers
text/plain 774b
On Mon, Aug 17, 2009 at 09:33:35AM -0400, John Napiorkowski via RT wrote: Show quoted text
> Honestly the only thing I can think of is to either 1) rewrite the tests > so that all these bits don't need to be equal or 2) skip the tests in > cases where the fine grained time module is not present. > > 1 Is probably the only way we are going to fix it for certain.
Actually, extending DBIx::Class::DynamicDefault to give it some functionality to invoke a callback only once for a set of columns. Using that would get rid of the race condition that makes these tests fail. I'd suggest something like dynamic_default_on_update => \'some_other_column' to declare combined or dependant or whatever dynamic defaults. -- BOFH excuse #365: parallel processors running perpendicular today
Download signature.asc
application/pgp-signature 189b

Message body not shown because it is not plain text.

Download (untitled) / with headers
text/plain 612b
Show quoted text
> Actually, extending DBIx::Class::DynamicDefault to give it some > functionality to invoke a callback only once for a set of columns. > > Using that would get rid of the race condition that makes these tests > fail. > > I'd suggest something like > > dynamic_default_on_update => \'some_other_column' > > to declare combined or dependant or whatever dynamic defaults.
Sounds reasonable but at the moment we cannot guarantee the created/updated timestamps to be equal (and it is a question whether we need to) therefore we probably should not test it. So, I vote for skipping the test for now. -- kmx
I also get this one-second difference in t/06timestamp.t

Show quoted text
#   Failed test 'update and create timestamp'
#   at t/06timestamp.t line 28.
#          got: '2010-05-22T00:18:55'
#     expected: '2010-05-22T00:18:54'
# Looks like you failed 1 test of 3.

Strawberry Perl 5.10.1.

Maybe just implement a one-second tolerance in the test?


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.