Re: [Postgres-xc-developers] Running regression test.

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Thank you Tomonori and Abbas;

To run make installcheck, we need to setup PG* environemnt for the
installation/configuration.   To make it simpler, we may need some
improvement in the regression as well (to specify target port and host).

Regards;

----------
Koichi Suzuki

2013/7/8 Abbas Butt <abb...@en...>

>
>
> On Mon, Jul 8, 2013 at 12:55 PM, Tomonari Katsumata <
> kat...@po...> wrote:
>
>> Hi,
>>
>> I've tried regression test with Postgres-XC master, it didn't work.
>> Now, I've tried it with 1.1beta, but it didn't work too.
>>
>> =========================
>> 58 of 153 tests failed.
>> =========================
>>
>> My test environment is below.
>> ----
>> server : CentOS 6.4 x86_64 on VMWare player
>> cpu : Intel(R) Core(TM) i3-2370M CPU @2.40GHz(1core assigned)
>> memory : 256MB
>> dbms : Postgres-XC 1.1beta
>> ----
>> all components are in one server.
>> (please see "pgxc_ctl.conf")
>>
>> And the procedure is below.
>> ============================================
>> 1. build Postgres-XC and pgxc_ctl
>>
>> ./configure --enable-debug CFLAGS='-O0'
>> make
>> sudo make install
>> cd contrib/pgxc_ctl
>> make
>> sudo make install
>>
>> 2. init Postgres-XC with pgxc_ctl
>> pgxc_ctl init all
>>
>> 3. start regression test
>> make installcheck
>> ============================================
>> Did I do something wrong ??
>>
>
> No.
>
>
>>
>> The log messages says Postgres-XC (coordinator) crashed when
>> processing xmlmap test.
>> This is same scenario with the behavior of master.
>> ----
>> LOG: server process (PID 14567) was terminated by signal 11:
>> Segmentation fault
>> DETAIL: Failed process was running: DECLARE xc CURSOR WITH HOLD FOR
>> SELECT * FROM testxmlschema.test1 ORDER BY 1, 2;
>> LOG: terminating any other active server processes
>> WARNING: terminating connection because of crash of another server process
>> DETAIL: The postmaster has commanded this server process to roll back
>> the current transaction and exit, because another server process exited
>> abnormally and possibly corrupted shared memory.
>> HINT: In a moment you should be able to reconnect to the database and
>> repeat your command.
>> LOG: archiver process (PID 13432) exited with exit code 1
>> LOG: all server processes terminated; reinitializing
>> FATAL: the database system is in recovery mode
>> LOG: database system was interrupted; last known up at 2013-07-07
>> 22:29:16 PDT
>> LOG: database system was not properly shut down; automatic recovery in
>> progress
>> FATAL: the database system is in recovery mode
>> ----
>>
>> Is this a problem or not problem ?
>>
>
> This is a problem.
>
>
>> Anybody runs all regression test cases ?
>>
>
> We do, but not with 1 coordinator and 1 datanode like you did.
>
>
>> What should I do to run all ?
>>
>
> I was able to reproduce the crash. Actually there are multiple crashes.
> The crash happens when we run regression with 1 coordinator and 1 datanode
> that happens to be primary.
>
> The first crash (an assertion failure on the datanode) can be reproduced
> using this test case (aggregates.sql)
>
> create table varchar_tbl( f1 character varying(4) );
> insert into varchar_tbl values('a'), ('ab'), ('abcd'), ('abcd');
> select string_agg(distinct f1, ',' order by f1) from varchar_tbl;
>
> It would cause a datanode crash
>
> TRAP: FailedAssertion("!(AggCheckCallContext(fcinfo, ((void *)0)))", File:
> "varlena.c", Line: 3668)
>
> The second crash (an assertion failure on coordinator) can be reproduced
> using this test case (xmlmap.sql)
> CREATE SCHEMA testxmlschema;
> CREATE TABLE testxmlschema.test1 (a int, b text);
> INSERT INTO testxmlschema.test1 VALUES (1, 'one'), (2, 'two'), (-1, null);
>
>
> DECLARE xc CURSOR WITH HOLD FOR SELECT * FROM testxmlschema.test1 ORDER BY
> 1, 2;
>
> TRAP: BadArgument("!(((header->context) != ((void *)0) && (((((const
> Node*)((header->context)))->type) == T_AllocSetContext))))", File:
> "mcxt.c", Line: 660)
>
> To be able to run the regression with 1 coordinator and 1 datanode we need
> to fix these two issues first and then see whether we have any additional
> case to fix.
>
> Special thanks to Tomonari for the efforts that led to discovery of these
> errors.
>
> I am going to spend some time to try and fix these errors. Any other
> suggestion is welcome.
>
>
>
>>
>> regards,
>> ----------
>> NTT Software Corporation
>> Tomonari Katsumata
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>>
>> Build for Windows Store.
>>
>> http://p.sf.net/sfu/windows-dev2dev
>> _______________________________________________
>> Postgres-xc-developers mailing list
>> Pos...@li...
>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>
>>
>
>
> --
> --
> *Abbas*
>  Architect
>
> Ph: 92.334.5100153
>  Skype ID: gabbasb
> www.enterprisedb.co <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
> *
> Follow us on Twitter*
> @EnterpriseDB
>
> Visit EnterpriseDB for tutorials, webinars, whitepapers<http://www.enterprisedb.com/resources-community>and more<http://www.enterprisedb.com/resources-community>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>
>