Re: [HACKERS] intermittent failures in Cygwin from select_parallel tests - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] intermittent failures in Cygwin from select_parallel tests
Date
Msg-id 2118.1496674747@sss.pgh.pa.us
Whole thread Raw
In response to [HACKERS] intermittent failures in Cygwin from select_parallel tests  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
List pgsql-hackers
Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:
> Buildfarm member lorikeet is failing occasionally with a failed
> assertion during the select_parallel regression tests like this:

>     2017-06-03 05:12:37.382 EDT [59327d84.1160:38] LOG:  statement: select count(*) from tenk1, tenk2 where
tenk1.hundred> 1 and tenk2.thousand=0; 
>     TRAP: FailedAssertion("!(vmq->mq_sender == ((void *)0))", File:
"/home/andrew/bf64/root/HEAD/pgsql.build/../pgsql/src/backend/storage/ipc/shm_mq.c",Line: 221) 

> I'll see if I can find out why, but if anyone has any ideas why this might be happening (started about 3 weeks ago)
thatwould be helpful. 

Well, this seems like it has to indicate an incorrect call of
shm_mq_set_sender.  I have no great insights as to what might be causing
that, but I sure find it to be pretty unacceptable coding practice that
the call sites are not checking for failure returns from shm_toc_lookup.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: [HACKERS] intermittent failures in Cygwin from select_parallel tests
Next
From: Dilip Kumar
Date:
Subject: Re: [HACKERS] Default Partition for Range