Re: Please test DBI-1.628_50 re change in PrintWarn

2013-10-11 Thread Tim Bunce
NOTE: this trial version of the DBI requires compiled drivers to be recompiled.

So if you install it, you'll break all your compiled drivers untill tou
recompile and reinstall them.

I'm not sure yet if the final DBI-1.629 release will have that requirement.
(If it doesn't, and you've installed this trial version, then you'll
need to recompile your drivers again. Sorry for the inconvenience!)

Tim.

On Fri, Oct 11, 2013 at 01:49:04PM +0100, Tim Bunce wrote:
> The PrintWarn attribute used to default to the same value as $^W.
> In other words, if you ran perl with -w then would be on.
> 
> See https://metacpan.org/module/TIMB/DBI-1.627/DBI.pm#PrintWarn
> 
> That was reasonable back in early 2004 when PrintWarn was added to the
> DBI.  I'm planning to change PrintWarn to always default on.
> 
> There's a small risk that this change will cause extra warnings to be
> logged from your application if it's doing something that triggers the
> driver to record warning states (via the set_err method).
> 
> I've uploaded DBI-1.628_50 as a trial release of DBI-1.629 so you can
> test it *with your application code* (not just make test) and report back.
> 
> Please report back whether you have extra warnings logged *OR NOT*
> and don't forget to mention what driver you're using.
> 
> Thanks!
> 
> Tim.
> 
> p.s. DBI-1.628_50 will install as $DBI::VERSION 1.629.
> Changes: 
> https://metacpan.org/changes/release/TIMB/DBI-1.628_50#Changes-in-DBI-1.629


Re: Please test DBI-1.628_50 re change in PrintWarn

2013-10-11 Thread H.Merijn Brand
On Fri, 11 Oct 2013 13:49:04 +0100, Tim Bunce 
wrote:

> The PrintWarn attribute used to default to the same value as $^W.
> In other words, if you ran perl with -w then would be on.
> 
> See https://metacpan.org/module/TIMB/DBI-1.627/DBI.pm#PrintWarn
> 
> That was reasonable back in early 2004 when PrintWarn was added to the
> DBI.  I'm planning to change PrintWarn to always default on.
> 
> There's a small risk that this change will cause extra warnings to be
> logged from your application if it's doing something that triggers the
> driver to record warning states (via the set_err method).
> 
> I've uploaded DBI-1.628_50 as a trial release of DBI-1.629 so you can
> test it *with your application code* (not just make test) and report back.
> 
> Please report back whether you have extra warnings logged *OR NOT*
> and don't forget to mention what driver you're using.
> 
> Thanks!
> 
> Tim.
> 
> p.s. DBI-1.628_50 will install as $DBI::VERSION 1.629.
> Changes: 
> https://metacpan.org/changes/release/TIMB/DBI-1.628_50#Changes-in-DBI-1.629

Merging with dbi-test-conditional caused a bit of a delay

Testing all on git checkouts …

### DBI

All tests successful.
Files=183, Tests=11441, 88 wallclock secs ( 1.86 usr  0.28 sys + 70.62 cusr  
7.05 csys = 79.81 CPU)
Result: PASS
PERL_DL_NONLAZY=1 /pro/bin/perl5.18.0 "-Iblib/lib" "-Iblib/arch" test.pl

### SQL-Statement - dbi-test branch

Test Summary Report
---
t/06virtual.t  (Wstat: 0 Tests: 2714 Failed: 0)
  TODO passed:   587-589, 1264-1266, 1943-1945, 2622-2624
t/08join.t (Wstat: 0 Tests: 1284 Failed: 0)
  TODO passed:   289-291, 293-295, 314, 316, 318, 321, 610-612
614-616, 635, 637, 639, 642, 931-933, 935-937
956, 958, 960, 963, 1252-1254, 1256-1258
1277, 1279, 1281, 1284
xt/pod_coverage.t  (Wstat: 1280 Tests: 21 Failed: 5)
  Failed tests:  15, 17-20
  Non-zero exit status: 5
Files=91, Tests=10628, 38 wallclock secs ( 1.36 usr  0.17 sys + 32.57 cusr  
1.84 csys = 35.94 CPU)
Result: FAIL
Failed 1/91 test programs. 5/10628 subtests failed.

### DBD-CSV

Text::CSV_XS-1.02

All tests successful.
Files=185, Tests=6659, 51 wallclock secs ( 1.27 usr  0.24 sys + 45.35 cusr  
3.50 csys = 50.36 CPU)
Result: PASS
All tests successful.
Files=23, Tests=607,  4 wallclock secs ( 0.15 usr  0.04 sys +  3.07 cusr  0.31 
csys =  3.57 CPU)
Result: PASS

### DBD-Pg (used the github clone instead of the bucardo.org one. which is
canonical?)

psql (PostgreSQL) 9.3.0

All tests successful.
Files=21, Tests=1715, 42 wallclock secs ( 0.32 usr  0.04 sys +  5.58 cusr  1.30 
csys =  7.24 CPU)
Result: PASS

### DBD-mysql

Test Summary Report
---
t/29warnings.t (Wstat: 65280 Tests: 5 Failed: 0)
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 8 tests but ran 5.
t/31insertid.t (Wstat: 65280 Tests: 2 Failed: 0)
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 18 tests but ran 2.
t/40bindparam2.t   (Wstat: 65280 Tests: 2 Failed: 0)
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 13 tests but ran 2.
t/40blobs.t(Wstat: 65280 Tests: 3 Failed: 0)
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 14 tests but ran 3.
t/40catalog.t  (Wstat: 65280 Tests: 71 Failed: 0)
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 78 tests but ran 71.
t/40listfields.t   (Wstat: 65280 Tests: 3 Failed: 0)
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 25 tests but ran 3.
t/87async.t(Wstat: 65280 Tests: 77 Failed: 25)
  Failed tests:  5-6, 11, 13-14, 18-22, 40-45, 51-52, 55-56
58, 73, 75-77
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 92 tests but ran 77.
t/88async-multi-stmts.t(Wstat: 512 Tests: 8 Failed: 2)
  Failed tests:  7-8
  Non-zero exit status: 2
t/89async-method-check.t   (Wstat: 2048 Tests: 223 Failed: 8)
  Failed tests:  207, 209, 211, 213, 215, 217, 219, 221
  Non-zero exit status: 8
Files=53, Tests=1212, 24 wallclock secs ( 0.45 usr  0.07 sys +  2.61 cusr  0.45 
csys =  3.58 CPU)
Result: FAIL
Failed 9/53 test programs. 35/1212 subtests failed.

### DBD-Oracle - looks like github.com:yanick/DBD-Oracle.git is dead
 long live  github.com:gwenshap/DBD-Oracle.git ?
Note that Makefile.PL *still* notes the yanick version as repo source

Oracle version 12.1.0.1 (12.1)

cc -c  -I/usr/include/oracle/12.1/client  
-I/pro/3gl/CPAN/DBI/blib/arch/auto/DBI -fno-strict-aliasing -pipe 
-fstack-protector -I/pro/local/include -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -O3   -DVERSION=\"1.33_00\" -DXS_VERSION=\"1.33_00\" 
-fPIC "-I/pro/lib/perl5/5.18.0/i686-linux-64int-ld/CORE"  -Wall -Wno-comment 
-DUTF8_SUPPORT -DORA_OCI_VERSION=\"12.1.0.1\" -DORA_OCI_102 -DORA_OCI

Please test DBI-1.628_50 re change in PrintWarn

2013-10-11 Thread Tim Bunce
The PrintWarn attribute used to default to the same value as $^W.
In other words, if you ran perl with -w then would be on.

See https://metacpan.org/module/TIMB/DBI-1.627/DBI.pm#PrintWarn

That was reasonable back in early 2004 when PrintWarn was added to the
DBI.  I'm planning to change PrintWarn to always default on.

There's a small risk that this change will cause extra warnings to be
logged from your application if it's doing something that triggers the
driver to record warning states (via the set_err method).

I've uploaded DBI-1.628_50 as a trial release of DBI-1.629 so you can
test it *with your application code* (not just make test) and report back.

Please report back whether you have extra warnings logged *OR NOT*
and don't forget to mention what driver you're using.

Thanks!

Tim.

p.s. DBI-1.628_50 will install as $DBI::VERSION 1.629.
Changes: 
https://metacpan.org/changes/release/TIMB/DBI-1.628_50#Changes-in-DBI-1.629