[ledgersmb-devel] Re: PGObject-Util-DBAdmin-1.0.3 testing problems with PostgreSQL

Hi Chris,

Thanks for your report and continued efforts!

I recently released PGObject::Util::DBAdmin-1.1.0; please port that instead of 1.0.3: LedgerSMB 1.9 will depend on it.

As for testing on FreeBSD not working out of the box: I don't understand the issue, because it was successfully tested on CPANTESTERS on 191 testers, including FreeBSD testers: http://matrix.cpantesters.org/?dist=PGObject-Util-DBAdmin+1.0.3

Regarding the 02dbexceptions.t test succeeding with and without a password: I'm expecting that to be a local setup issue. Many PostgreSQL setups don't require a password for the "postgres" user when connecting from the 'postgres' system account.

Regards,

Erik

On Thu, Aug 27, 2020 at 8:13 PM Chris Bennett <..hidden..> wrote:

Hi,

I'm testing with PostgreSQL, but it does not pass as-is.

t/var directory is missing. If I manually create it, it works.

Second, the password for user postgres is missing in 01.1-dbtests.t
on line 19 where it is set as undef.
the same within 01.2-backup_globals.t on line 21.

If I create var and put in the password for postgres (default user in
OpenBSD), then everything passes.

The two requests for a password from 02-dbexceptions.t work with or
without a real password. That would mean needing to run the testing
interactively, also. That is OK, but I would prefer to put that in to
make everything happen non-interactively. I can dig into the code to
fidure out where to add this to the tests.

Is this an existing problem that needs to be patched? Either at my end
or in LedgerSMB?

OpenBSD always runs tests within an infrastructure and never directly
with the perl testing.

I'll submit this to ports, but I still need to deal with doing this the
best way first.

Thanks,
Chris Bennett

Bye,

Erik.

http://efficito.com -- Hosted accounting and ERP.

Robust and Flexible. No vendor lock-in.