Re: 15beta1 test failure on mips in isolation/expected/stats - Mailing list pgsql-hackers

From Kyotaro Horiguchi
Subject Re: 15beta1 test failure on mips in isolation/expected/stats
Date
Msg-id 20220520.131209.402179250617578251.horikyota.ntt@gmail.com
Whole thread Raw
In response to Re: 15beta1 test failure on mips in isolation/expected/stats  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
At Thu, 19 May 2022 22:58:14 -0400, Tom Lane <tgl@sss.pgh.pa.us> wrote in 
> Kyotaro Horiguchi <horikyota.ntt@gmail.com> writes:
>     Notice that these markers can only delay reporting of the completion
>     of a step, not the launch of a step.  The isolationtester will launch
>     the next step in a permutation as soon as (A) all prior steps of the
>     same session are done, and (B) the immediately preceding step in the
>     permutation is done or deemed blocked.  For this purpose, "deemed
>     blocked" means that it has been seen to be waiting on a database lock,
>     or that it is complete but the report of its completion is delayed by
>     one of these markers.
> 
> There's no "waiting..." reports in the test output, nor do we have any
> condition markers in stats.spec right now, so I don't think any steps
> have been "deemed blocked".

Mmm... Thanks. I miunderstood the effect of it..

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: 15beta1 test failure on mips in isolation/expected/stats
Next
From: Natarajan R
Date:
Subject: Re: Valgrind mem-check for postgres extension