Thread: 8.3.3 regression test on SCO 5.0.7
Hi All, I have been working through upgrades on legacy business systems on old Linux and SCO plateforms. With the help of this list the Linux problems are handled, thanks. The SCO build is not yet done. I have managed to compile 8.3.3 with the help of the archives. But there were lots of warnings and I would like to see the results of the regression tests. I'm looking for help to make the regression tests happen. Thanks Allan make check at the top level fails with: Running in noclean mode. Mistakes will not be cleaned up. could not determine encoding for locale "C_C.C": codeset is "" initdb: could not find suitable encoding for locale C_C.C Rerun initdb with the -E option. Try "initdb --help" for more information. The files belonging to this database system will be owned by user "postgres". This user must also own the server process. The database cluster will be initialized with locale C_C.C. Moving to ......./postgresql-8.3.3/src/test/regress and running ./pg_regress --temp-install=./tmp_check --top-builddir=../../.. --srcdir=/upgrades/postgres/postgresql-8.3.3/src/test/regress--temp-port=55432 --schedule=./parallel_schedule --multibyte=SQL_ASCII--load-language=plpgsql --no-locale ( note the added --no-locale ) gets me further, but fails with: Running in noclean mode. Mistakes will not be cleaned up. The files belonging to this database system will be owned by user "postgres". This user must also own the server process. The database cluster will be initialized with locale C. The default database encoding has accordingly been set to SQL_ASCII. The default text search configuration will be set to "english". creating directory /upgrades/postgres/postgresql-8.3.3/src/test/regress/./tmp_che ck/data ... ok creating subdirectories ... ok selecting default max_connections ... 100 selecting default shared_buffers/max_fsm_pages ... 32MB/204800 creating configuration files ... ok creating template1 database in /upgrades/postgres/postgresql-8.3.3/src/test/regre ss/./tmp_check/data/base/1 ... =: is not an identifier child process exited with exit code 1 initdb: data directory "/upgrades/postgres/postgresql-8.3.3/src/test/regress/./tm p_check/data" not removed at user's request The material contained in this email may be confidential, privileged or copyrighted. If you are not the intended recipient,use, disclosure or copying of this information is prohibited. If you have received this document in error, pleaseadvise the sender and delete the document. Neither OneSteel nor the sender accept responsibility for any viruses containedin this email or any attachments.
"Harvey, Allan AC" <HarveyA@OneSteel.com> writes:
> creating template1 database in /upgrades/postgres/postgresql-8.3.3/src/test/regre
> ss/./tmp_check/data/base/1 ... =: is not an identifier
I'd guess you have an incompatible awk or possibly sed. Look at the
postgres.bki file generated on this system and compare it to one
generated from 8.3 on a non-broken system. It might or might not
be easy to determine exactly where the breakage is, but I suspect the
short answer is going to be "install gawk".
regards, tom lane
> "Harvey, Allan AC" <HarveyA@OneSteel.com> writes: > > creating template1 database in > /upgrades/postgres/postgresql-8.3.3/src/test/regre > > ss/./tmp_check/data/base/1 ... =: is not an identifier > > I'd guess you have an incompatible awk or possibly sed. Look at the > postgres.bki file generated on this system and compare it to one > generated from 8.3 on a non-broken system. It might or might not > be easy to determine exactly where the breakage is, but I suspect the > short answer is going to be "install gawk". > > regards, tom lane A diff of postgres.bki on the SCO system to another that completed the regression tests OK produced no differences. Slapped GNU Awk 3.1.1 over the top of the SCO distributed awk. No difference. Looking into sed now. Ta, Allan The material contained in this email may be confidential, privileged or copyrighted. If you are not the intended recipient,use, disclosure or copying of this information is prohibited. If you have received this document in error, pleaseadvise the sender and delete the document. Neither OneSteel nor the sender accept responsibility for any viruses containedin this email or any attachments.
"Harvey, Allan AC" <HarveyA@OneSteel.com> writes:
>> "Harvey, Allan AC" <HarveyA@OneSteel.com> writes:
>>> creating template1 database in /upgrades/postgres/postgresql-8.3.3/src/test/regress/./tmp_check/data/base/1 ... =:
isnot an identifier
> A diff of postgres.bki on the SCO system to another that completed the regression
> tests OK produced no differences.
Huh ... so much for the easy theory. What you need to do next is figure
out exactly where the failure is coming from. Try running initdb with
--debug option (this will produce LOTS of stuff on stderr), and post the
last hundred or so lines of debug output.
regards, tom lane
> "Harvey, Allan AC" <HarveyA@OneSteel.com> writes:
> >> "Harvey, Allan AC" <HarveyA@OneSteel.com> writes:
> >>> creating template1 database in
> /upgrades/postgres/postgresql-8.3.3/src/test/regress/./tmp_che
> ck/data/base/1 ... =: is not an identifier
>
> > A diff of postgres.bki on the SCO system to another that
> completed the regression
> > tests OK produced no differences.
>
> Huh ... so much for the easy theory. What you need to do
> next is figure
> out exactly where the failure is coming from. Try running initdb with
> --debug option (this will produce LOTS of stuff on stderr),
> and post the
> last hundred or so lines of debug output.
I don't think this is what you were expecting, I know I was not, but then I don't know much.
Allan
DEBUG: StartTransaction
DEBUG: name: unnamed; blockState: DEFAULT; state: INPROGR, xid/subid/cid: 0/1/0, nestlvl: 1, children:
DEBUG: start transaction
DEBUG: CommitTransaction
DEBUG: name: unnamed; blockState: STARTED; state: INPROGR, xid/subid/cid: 0/1/35, nestlvl: 1, children:
DEBUG: commit transaction
DEBUG: proc_exit(0)
DEBUG: shmem_exit(0)
DEBUG: exit(0)
ok
initializing pg_authid ... ok
initializing dependencies ... ok
creating system views ... ok
loading system objects' descriptions ... ok
creating conversions ... ok
creating dictionaries ... ok
setting privileges on built-in objects ... ok
creating information schema ... ok
vacuuming database template1 ... ok
copying template1 to template0 ... ok
copying template1 to postgres ... ok
WARNING: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the -A option the
next time you run initdb.
Success. You can now start the database server using:
/upgrades/postgres/postgresql-8.3.3/src/test/regress/./tmp_check/install//usr/local/pgsql/bin/postgres -D
/upgrades/postgres/postgresql-8.3.3/src/test/regress/./tmp_check/data
or
/upgrades/postgres/postgresql-8.3.3/src/test/regress/./tmp_check/install//usr/local/pgsql/bin/pg_ctl -D
/upgrades/postgres/postgresql-8.3.3/src/test/regress/./tmp_check/data-l logfile start
The material contained in this email may be confidential, privileged or copyrighted. If you are not the intended
recipient,use, disclosure or copying of this information is prohibited. If you have received this document in error,
pleaseadvise the sender and delete the document. Neither OneSteel nor the sender accept responsibility for any viruses
containedin this email or any attachments.
> "Harvey, Allan AC" <HarveyA@OneSteel.com> writes: > >> "Harvey, Allan AC" <HarveyA@OneSteel.com> writes: > >>> creating template1 database in > /upgrades/postgres/postgresql-8.3.3/src/test/regress/./tmp_che > ck/data/base/1 ... =: is not an identifier > > > A diff of postgres.bki on the SCO system to another that > completed the regression > > tests OK produced no differences. > > Huh ... so much for the easy theory. What you need to do > next is figure > out exactly where the failure is coming from. Try running initdb with > --debug option (this will produce LOTS of stuff on stderr), > and post the > last hundred or so lines of debug output. > > regards, tom lane > This is mainly for the archives should someone else like to beat SCO into partial submission.... Regression testing does not work for reasons I don't know when attempting them from the makefiles. ie make check. BUT screen scrapping the executed commands and/or suggestions does work. Here is what worked ( scrapped from bash history, hope I go it right ). Substitute you own installation path. cd src/test/regress rm -r /upgrades/postgres/postgresql-8.3.3/src/test/regress/./tmp_check/data /upgrades/postgres/postgresql-8.3.3/src/test/regress/./tmp_check/install//usr/local/pgsql/bin/initdb -D /upgrades/postgres/postgresql-8.3.3/src/test/regress/./tmp_check/data-L /upgrades/postgres/postgresql-8.3.3/src/test/regress/./tmp_check/install/usr/local/pgsql/share--noclean --no-locale /upgrades/postgres/postgresql-8.3.3/src/test/regress/./tmp_check/install//usr/local/pgsql/bin/postgres -D /upgrades/postgres/postgresql-8.3.3/src/test/regress/./tmp_check/data In another shell... cd src/test/regress ./pg_regress --psqldir=/upgrades/postgres/postgresql-8.3.3/src/test/regress/./tmp_check/install//usr/local/pgsql/bin --schedule=./serial_schedule--srcdir=/upgrades/postgres/postgresql-8.3.3/src/test/regress --multibyte=SQL_ASCII --load-language=plpgsql--host=localhost All tests passed, save for those that use "Infinity" and "NaN" and variants on that theme. I can post regression.diffs should anyone want them. Regression testing is however the end of the story, getting it compiled was the main effort. Summarised here: Get GNU gawk and tar and substitute the SCO distributed versions. Do not use the SCO Open server development environment ( export CC=cc; ./configure; etc etc ) as 64 bit is not supportedan even more regression tests fail. The Unixware and OpenServer Development Kit compiles nicely, but promptly core dumps with unsupported system calls in thecompatibility module or some such. Attempting to use the Skunkware gcc (2.95.3) fails in ./configure ( export CC=gcc ). With the help of http://archives.postgresql.org/pgsql-bugs/2001-06/msg00141.php and http://archives.postgresql.org/pgsql-ports/2008-06/msg00001.php The correct options can be given to gcc. src/makefiles/Makefile.sco is the wrong place, see link above, /src/template/sco is the right place and I made it #CC="$CC -b elf" CC="$CC -melf" The make worked which lead to the regression testing, see above. Note UNIX sockets seem broken for get/setsockopt() so always connect over TCP/IP. ie --host=localhost seems to work aroundit. Hope this helps someone else. Now to the actuall upgrade..... Allan The material contained in this email may be confidential, privileged or copyrighted. If you are not the intended recipient,use, disclosure or copying of this information is prohibited. If you have received this document in error, pleaseadvise the sender and delete the document. Neither OneSteel nor the sender accept responsibility for any viruses containedin this email or any attachments.