Bug #92413 for DBD-SQLite: 1.40 fails a test under the 5.8.9 provided by Travis-CI

Thu Jan 23 11:14:24 2014 ribasushi [...] leporine.io - Ticket created

Subject:

1.40 fails a test under the 5.8.9 provided by Travis-CI

Relevant log attached below, the entire install can be found at https://api.travis-ci.org/jobs/17484750/log.txt?deansi=true ... # Failed test 'no warnings' # at inc/Test/NoWarnings.pm line 38. # There were 1 warning(s) # Previous test 0 '' # Argument "2.07_02" isn't numeric in subroutine entry at /home/travis/perl5/perlbrew/perls/5.8/lib/5.8.9/File/Temp.pm line 14. # at /home/travis/perl5/perlbrew/perls/5.8/lib/5.8.9/File/Temp.pm line 14. # File::Temp::BEGIN() called at /home/travis/perl5/perlbrew/perls/5.8/lib/5.8.9/File/Path.pm line 14 # eval {...} called at /home/travis/perl5/perlbrew/perls/5.8/lib/5.8.9/File/Path.pm line 14 # require File/Temp.pm called at t/33_non_latin_path.t line 22 # main::BEGIN() called at /home/travis/perl5/perlbrew/perls/5.8/lib/5.8.9/File/Path.pm line 14 # eval {...} called at /home/travis/perl5/perlbrew/perls/5.8/lib/5.8.9/File/Path.pm line 14 # # Looks like you failed 1 test of 27. [16:09:10] t/33_non_latin_path.t ....................... Dubious, test returned 1 (wstat 256, 0x100) ...

Thu Jan 23 12:43:59 2014 ishigaki [...] cpan.org - Correspondence added

Thanks for the heads-up. CPAN testers reported me the same as well. I disabled Test::NoWarning for the test in DBD::SQLite 1.41_05 (which will hopefully be 1.42) and it seems ok as of this writing. http://www.cpantesters.org/distro/D/DBD-SQLite.html#DBD-SQLite-1.41_05 On Fri Jan 24 01:14:24 2014, RIBASUSHI wrote: Show quoted text

> Relevant log attached below, the entire install can be found at > https://api.travis-ci.org/jobs/17484750/log.txt?deansi=true > > ... > # Failed test 'no warnings' > # at inc/Test/NoWarnings.pm line 38. > # There were 1 warning(s) > # Previous test 0 '' > # Argument "2.07_02" isn't numeric in subroutine entry at > /home/travis/perl5/perlbrew/perls/5.8/lib/5.8.9/File/Temp.pm line 14. > # at /home/travis/perl5/perlbrew/perls/5.8/lib/5.8.9/File/Temp.pm > line 14. > # File::Temp::BEGIN() called at > /home/travis/perl5/perlbrew/perls/5.8/lib/5.8.9/File/Path.pm line 14 > # eval {...} called at > /home/travis/perl5/perlbrew/perls/5.8/lib/5.8.9/File/Path.pm line 14 > # require File/Temp.pm called at t/33_non_latin_path.t line 22 > # main::BEGIN() called at > /home/travis/perl5/perlbrew/perls/5.8/lib/5.8.9/File/Path.pm line 14 > # eval {...} called at > /home/travis/perl5/perlbrew/perls/5.8/lib/5.8.9/File/Path.pm line 14 > # > # Looks like you failed 1 test of 27. > [16:09:10] t/33_non_latin_path.t ....................... > Dubious, test returned 1 (wstat 256, 0x100) > ...

Thu Jan 23 12:44:00 2014 The RT System itself - Status changed from 'new' to 'open'

Thu Jan 23 12:48:51 2014 ribasushi [...] leporine.io - Correspondence added

On Thu Jan 23 18:43:59 2014, ISHIGAKI wrote: Show quoted text

> Thanks for the heads-up. CPAN testers reported me the same as well. I > disabled Test::NoWarning for the test in DBD::SQLite 1.41_05 (which > will hopefully be 1.42) and it seems ok as of this writing. >

Ah, sorry for the duplicate then. Though it is partly your fault - you mark tickets with unreleased fixes as "resolved" immediately. If you mark them as "patched" instead they will still show up in the main list, so someone like me can quickly see it is already taken care of (also patched does not count towards your bug amount). For instance: https://rt.cpan.org/Dist/Display.html?Queue=DBIx-Class Cheers!

Thu Jan 23 12:48:52 2014 ribasushi [...] leporine.io - Status changed from 'open' to 'patched'

Thu Jan 23 14:05:01 2014 ishigaki [...] cpan.org - Correspondence added

On Fri Jan 24 02:48:51 2014, RIBASUSHI wrote: Show quoted text

> On Thu Jan 23 18:43:59 2014, ISHIGAKI wrote:

> > Thanks for the heads-up. CPAN testers reported me the same as well. I > > disabled Test::NoWarning for the test in DBD::SQLite 1.41_05 (which > > will hopefully be 1.42) and it seems ok as of this writing. > >

> > Ah, sorry for the duplicate then. Though it is partly your fault - you > mark tickets with unreleased fixes as "resolved" immediately. If you > mark them as "patched" instead they will still show up in the main > list, so someone like me can quickly see it is already taken care of > (also patched does not count towards your bug amount).

Hm. I usually mark "patched" when I apply a fix in the repository, and mark "resolved" when I release a dev version. Maybe I can wait till I release a stable version, though. Show quoted text

> > For instance: https://rt.cpan.org/Dist/Display.html?Queue=DBIx-Class > > Cheers!

Fri Mar 21 03:05:12 2014 ishigaki [...] cpan.org - Correspondence added

Closed this ticket as DBD::SQLite 1.42 was released. Thanks. On Fri Jan 24 04:05:01 2014, ISHIGAKI wrote: Show quoted text

> On Fri Jan 24 02:48:51 2014, RIBASUSHI wrote:

> > On Thu Jan 23 18:43:59 2014, ISHIGAKI wrote:

> > > Thanks for the heads-up. CPAN testers reported me the same as well. > > > I > > > disabled Test::NoWarning for the test in DBD::SQLite 1.41_05 (which > > > will hopefully be 1.42) and it seems ok as of this writing. > > >

> > > > Ah, sorry for the duplicate then. Though it is partly your fault - > > you > > mark tickets with unreleased fixes as "resolved" immediately. If you > > mark them as "patched" instead they will still show up in the main > > list, so someone like me can quickly see it is already taken care of > > (also patched does not count towards your bug amount).

> > Hm. I usually mark "patched" when I apply a fix in the repository, and > mark "resolved" when I release a dev version. Maybe I can wait till I > release a stable version, though. >

> > > > For instance: https://rt.cpan.org/Dist/Display.html?Queue=DBIx-Class > > > > Cheers!

Fri Mar 21 03:05:13 2014 ishigaki [...] cpan.org - Status changed from 'patched' to 'resolved'