| From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
|---|---|
| To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
| Cc: | myon(at)debian(dot)org, andres(at)anarazel(dot)de, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: 15beta1 test failure on mips in isolation/expected/stats |
| Date: | 2022-05-20 04:12:09 |
| Message-ID: | 20220520.131209.402179250617578251.horikyota.ntt@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At Thu, 19 May 2022 22:58:14 -0400, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote in
> Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Natarajan R | 2022-05-20 04:14:07 | Re: Valgrind mem-check for postgres extension |
| Previous Message | Andres Freund | 2022-05-20 03:59:28 | Re: 15beta1 test failure on mips in isolation/expected/stats |