Skip Menu |

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

Report information
The Basics
Id: 33308
Status: resolved
Priority: 0/
Queue: DBIx-Class

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

Bug Information
Severity: Important
Broken in: 0.08009
Fixed in: 0.08012



Subject: t/33storage_reconnect.t failing
t/33storage_reconnect.t is failing on my perl 5.10 on Arch Linux: [root@catalyst DBIx-Class-0.08009]# prove -b -v t/33storage_reconnect.t t/33storage_reconnect...... 1..5 ok 1 - Three artists returned DBI::db=HASH(0x8837640)->disconnect invalidates 22 active statement handles (either destroy statement handles or call finish on them before disconnecting) at t/33storage_reconnect.t line 23. closing dbh with active statement handles at t/33storage_reconnect.t line 23. ok 2 - Three artists returned Failed 3/5 subtests Test Summary Report ------------------- t/33storage_reconnect.t (Wstat: 11 Tests: 2 Failed: 0) Parse errors: Bad plan. You planned 5 tests but ran 2. Files=1, Tests=2, 0 wallclock secs ( 0.00 usr 0.00 sys + 0.20 cusr 0.04 csys = 0.24 CPU) Result: FAIL [root@catalyst DBIx-Class-0.08009]#
From: ntyni [...] iki.fi
On Sat Feb 16 16:26:13 2008, AMBS wrote: Show quoted text
> t/33storage_reconnect.t is failing on my perl 5.10 on Arch Linux: > > > [root@catalyst DBIx-Class-0.08009]# prove -b -v t/33storage_reconnect.t > t/33storage_reconnect...... > 1..5 > ok 1 - Three artists returned > DBI::db=HASH(0x8837640)->disconnect invalidates 22 active statement > handles (either destroy statement handles or call finish on them before > disconnecting) at t/33storage_reconnect.t line 23. > closing dbh with active statement handles at t/33storage_reconnect.t > line 23. > ok 2 - Three artists returned > Failed 3/5 subtests
This is caused by a long-standing bug in DBD-SQLite (tickets #30558 and #32100) that has become worse with SQLite 3.5, causing a segmentation fault here too. There's a fix outlined in those tickets that we have just applied into the Debian DBD-SQLite package. FWIW, this is also Debian bug #470272, http://bugs.debian.org/470272 . Cheers, -- Niko Tyni (Debian Perl Group) ntyni@debian.org
Subject: Re: [rt.cpan.org #33308] t/33storage_reconnect.t failing
Date: Tue, 11 Mar 2008 04:10:22 +0000
To: "ntyni [...] iki.fi via RT" <bug-DBIx-Class [...] rt.cpan.org>
From: Matt S Trout <mst [...] shadowcat.co.uk>
On Mon, Mar 10, 2008 at 03:39:06PM -0400, ntyni@iki.fi via RT wrote: Show quoted text
> > Queue: DBIx-Class > Ticket <URL: http://rt.cpan.org/Ticket/Display.html?id=33308 > > > On Sat Feb 16 16:26:13 2008, AMBS wrote:
> > t/33storage_reconnect.t is failing on my perl 5.10 on Arch Linux: > > > > > > [root@catalyst DBIx-Class-0.08009]# prove -b -v t/33storage_reconnect.t > > t/33storage_reconnect...... > > 1..5 > > ok 1 - Three artists returned > > DBI::db=HASH(0x8837640)->disconnect invalidates 22 active statement > > handles (either destroy statement handles or call finish on them before > > disconnecting) at t/33storage_reconnect.t line 23. > > closing dbh with active statement handles at t/33storage_reconnect.t > > line 23. > > ok 2 - Three artists returned > > Failed 3/5 subtests
> > This is caused by a long-standing bug in DBD-SQLite (tickets #30558 and > #32100) that has become worse with SQLite 3.5, causing a segmentation > fault here too. There's a fix outlined in those tickets that we have > just applied into the Debian DBD-SQLite package.
Could you comment to that effect in the DBD-SQLite queue, please? I get the feeling the patch went unapplied because the author hasn't had time to fully audit it so maybe the fact you've been able to apply and smoke test it will help push a fix upstream. -- Matt S Trout Need help with your Catalyst or DBIx::Class project? Technical Director http://www.shadowcat.co.uk/catalyst/ Shadowcat Systems Ltd. Want a managed development or deployment platform? http://chainsawblues.vox.com/ http://www.shadowcat.co.uk/servers/
The test suite now goes to greater lengths to diagnose and warn about a broken DBD::SQLite library. Although the mechanism is not perfect, it at least shows more information to the user. Also note that this is just a fix to properly warn about the problem - DBD::SQLite still needs upgrading.