perl 5.40.1 build: Possibly DBD::Oracle test t/rt85886.t will fail

[twata1]

Hello,

I split my issue with #231 .

Sample fail report:
http://www.cpantesters.org/cpan/report/ce9b4119-71da-1014-bef1-a252d96454ce

That test passes in perl 5.40.0 build .

Related to:
Failed test rt85886.t after DBI update #182

Thank you,

[shawnlaffan]

It would be good to know if this were due to Strawberry Perl or Perl itself. My assumption is the latter but I could be wrong.

Currently the only test runs on CPAN Testers are for Windows. The rest are NAs due to missing Oracle libs.

[shawnlaffan]

The same failure occurs for Perl 5.41.7 built using Visual Studio. That would suggest it is a Perl or DBD::Oracle problem.
https://www.cpantesters.org/cpan/report/26dac408-71e1-1014-8029-bc8b03dff4e4

[sisyphus]

I don't have Oracle either, but it It looks to me that fetchall_arrayref() must be returning the string '1', and that perl is correctly identifying it as such.
I'm thinking it's a problem with DBI and/or DBD::Oracle.

@twata, have you tried installing DBI from the https://github.com/perl5-dbi/dbi repo ?
What version of DBI is your Strawberry-5.40.1 using ?

[twata1]

@sisyphus
@twata, have you tried installing DBI from the https://github.com/perl5-dbi/dbi repo ?
No.

What version of DBI is your Strawberry-5.40.1 using ?
DBI version 1.647. It has been bundled with Strawberry-5.40.1 (strawberry-perl-5.40.1.1-64bit-portable-(dev_5401_20250124_gcc13)) from the beginning.

@shawnlaffan @sisyphus
It would be helpful if you could also refer to perl5-dbi/DBD-Oracle#182 .

Thank you,

[sisyphus]

DBI version 1.647. It has been bundled with Strawberry-5.40.1

Aaah, ok. I don't have that devel version. (Waiting for an official release.).

First thing I would try is the github version of DBI - and keep using it if all DBD::Oracle tests pass.

Otherwise .... is there any version of DBI that will work ok with DBD::Oracle on your SP-5.40.1 ? (1.646 looks a likely one, to me.)
If you could establish the latest version of DBI that will work with DBD::Oracle, then Shawn might agree to wind back to that version.
But only you can tell us what that version is.

[twata1]

Otherwise .... is there any version of DBI that will work ok with DBD::Oracle on your SP-5.40.1 ? (1.646 looks a likely one, to me.)
DBI version 1.645. The build log is attached.
build-DBD-Oracle-1.90-with-DBI-1.645.log

I could not build DBI version 1.646 on SP-5.40.1.
(See Also. http://fast-matrix.cpantesters.org/?dist=DBI%201.646)

Thank you,

[sisyphus]

I could not build DBI version 1.646 on SP-5.40.1.

It turns out that I could not build it either, on perl-5.40.0.

However, the github source (which reports itself as 1.648) is building without issue for me.
I gather that @Tux is the current maintainer. If we could tell him that the github source is working fine with DBD-Oracle-1.90 on WIndows, then he might be prepared to submit it as a new release to CPAN.

In case you're not really set up to obtain that github source, I will email you a tarball of it as soon as I've finished writing this post..
Maybe you could try building your DBD::Oracle against it, and see how that goes.

[twata1]

@sisyphus
I tried git clone from the repository and tested it, but the test did not PASS cleanly.
build-DBI-from-git-repositry.log

Relevant part of log:

(snip)

Files=200, Tests=8233, 199 wallclock secs ( 2.02 usr +  0.52 sys =  2.53 CPU)
Result: PASS
'env' is not recognized as an internal or external command,
operable program or batch file.
gmake: [makefile:1414: test] Error 1 (ignored)

C:\home\boxmandev001\dbi>

It is not clear whether the DBD::Oracle test can continue in this state.

[twata1]

Now I will try to test tarball which @sisyphus emailed me.

[twata1]

@sisyphus
Thank you for sending me the tarball by email.

Unfortunately, the situation did not change.
build logs are attached.

build-DBI-1.648(not-cpan-released).log
build-DBD-Oracle-1.90-with-DBI-1.648(not-cpan-released).log

Thank you,

[shawnlaffan]

The log files show all tests to be passing. There are some compilation warnings and a slew of uninitialised warnings from Text::Balanced but I cannot see anything that indicates that either DBI or DBI::Oracle do not work for those versions.

[sisyphus]

.... I cannot see anything that indicates that either DBI or DBI::Oracle do not work for those versions.

There's no apparent problem with DBI-1.645 (or earlier) and DBD-Oracle-1.90.
But DBI-1.646 is unbuildable (out of the box) and, according to the logs that @twata1 has provided, anything later than 1.646 (including current github version) results in DBD-Oracle-1.90 failing that one test in t/rt85886.t.

At least, that's how it appears to me.

[shawnlaffan]

.... I cannot see anything that indicates that either DBI or DBI::Oracle do not work for those versions.

There's no apparent problem with DBI-1.645 (or earlier) and DBD-Oracle-1.90. But DBI-1.646 is unbuildable (out of the box) and, according to the logs that @twata1 has provided, anything later than 1.646 (including current github version) results in DBD-Oracle-1.90 failing that one test in t/rt85886.t.

At least, that's how it appears to me.

Thanks Rob. Not sure what I was looking at earlier.

I'm still not convinced it's a Strawberry Perl specific problem, though, given the same failure manifests with a Visual Studio build of Perl 5.41.7 (https://www.cpantesters.org/cpan/report/26dac408-71e1-1014-8029-bc8b03dff4e4).

[sisyphus]

I'm still not convinced it's a Strawberry Perl specific problem, though,

Oh, I'm almost certain it's a bug in the relationship between DBI and DBD::Oracle - ie something that needs to be fixed in the DBI source and/or the DBD::Oracle source. Perhaps it could also be a bug in Oracle ... I dunno 'bout that.
I think the only decision for you to make is whether SP should ship with DBI-1.647 (knowing that this will cause DBD-Oracle-1.90 to fail a test) or should it ship with DBI-1.645 (which will allow DBD-Oracle-1.90 to build cleanly).

I don't know how significant that failure is, but if perl is receiving a PV when it should be receiving an IV then I can imagine that this might be cause for concern. (It would bother me.)

[shawnlaffan]

Thanks Rob. If there are no changes to DBI or DBI::Oracle in the meantime then we can keep DBI at 1.645.