Since the new parallel regression tests I've always had a few
lock NOTICE messages like the following.

In my latest run (from a CVS update today) I seem to have
a significantly higher level of failures and NOTICE messages.

I'm not sure where to look for the problem.

Platform Is Solaris 7 SPARC.

Here's just a sample from the 1st few parallel tests:-

bash-2.03$ ./checkresults | more
======   boolean   ======
0a1,2
> NOTICE:  LockRelease: locktable lookup failed, no lock
> NOTICE:  LockRelease: locktable lookup failed, no lock
======   varchar   ======
0a1,2
> NOTICE:  LockRelease: locktable lookup failed, no lock
> NOTICE:  LockRelease: xid table corrupted
======   int2   ======
0a1,4
> NOTICE:  LockRelease: locktable lookup failed, no lock
> NOTICE:  LockRelease: locktable lookup failed, no lock
> NOTICE:  LockRelease: locktable lookup failed, no lock
> NOTICE:  LockRelease: locktable lookup failed, no lock
10c14


Wed, 15 Dec 1999 23:33:17 +0000 (GMT)
Keith Parks <emkxp01@mtcc.demon.co.uk>
NOTICE:  LockRelease: locktable lookup failed, no lock
Keith Parks <emkxp01@mtcc.demon.co.uk> writes:
> Since the new parallel regression tests I've always had a few
> lock NOTICE messages like the following.

Interesting --- I had not run the parallel test for a while,
but I tried it just now and got half a dozen of these:
	NOTICE:  LockRelease: locktable lookup failed, no lock
(Otherwise the tests all passed.)

Something's been broken fairly recently.  Does anyone have an
idea what changed?

			regards, tom lane

Wed, 15 Dec 1999 22:36:37 -0500
Tom Lane <tgl@sss.pgh.pa.us>
Re: [HACKERS] NOTICE: LockRelease: locktable lookup failed, no lock 
> Keith Parks <emkxp01@mtcc.demon.co.uk> writes:
> > Since the new parallel regression tests I've always had a few
> > lock NOTICE messages like the following.
> 
> Interesting --- I had not run the parallel test for a while,
> but I tried it just now and got half a dozen of these:
> 	NOTICE:  LockRelease: locktable lookup failed, no lock
> (Otherwise the tests all passed.)
> 
> Something's been broken fairly recently.  Does anyone have an
> idea what changed?

Good question.  I can't imagine what it would be.  We didn't do much,
and parallel regression is not that old.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

Wed, 15 Dec 1999 22:46:31 -0500 (EST)
Bruce Momjian <pgman@candle.pha.pa.us>
Re: [HACKERS] NOTICE: LockRelease: locktable lookup failed, no lock
Bruce Momjian wrote:

> > Keith Parks <emkxp01@mtcc.demon.co.uk> writes:
> > > Since the new parallel regression tests I've always had a few
> > > lock NOTICE messages like the following.
> >
> > Interesting --- I had not run the parallel test for a while,
> > but I tried it just now and got half a dozen of these:
> >  NOTICE:  LockRelease: locktable lookup failed, no lock
> > (Otherwise the tests all passed.)
> >
> > Something's been broken fairly recently.  Does anyone have an
> > idea what changed?
>
> Good question.  I can't imagine what it would be.  We didn't do much,
> and parallel regression is not that old.

    While  building  the parallel test, I've ran the tests dozens
    of times to figure out which tests can be run grouped,  which
    not. Haven't seen such a message while doing so.

    Also,  I used it after another dozen times without. Now I see
    them too.  So I assume it was a recent change that introduced
    the problem.

    And  if  not,  much better. Would show that running all tests
    serialized had hidden a bug for a long time.


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#========================================= wieck@debis.com (Jan Wieck) #



Thu, 16 Dec 1999 13:08:32 +0100 (MET)
wieck@debis.com (Jan Wieck)
Re: [HACKERS] NOTICE: LockRelease: locktable lookup failed, no lock