| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Regina Obe" <lr(at)pcorp(dot)us> |
| Cc: | 'Juan José Santamaría Flecha' <juanjo(dot)santamaria(at)gmail(dot)com>, "'PostgreSQL mailing lists'" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #16920: Can't compile PostGIS with MingW64 against PostgreSQL 14 head |
| Date: | 2021-03-12 20:13:15 |
| Message-ID: | 2551612.1615579995@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Regina Obe" <lr(at)pcorp(dot)us> writes:
> There also seems to have been changes in code base since last I compiled that seemed to have helped a bit. Recompiling again with cassert - I get 1 fewer failure. I didn't check to see which test started passing.
In cases like this where some of the backends are actually crashing,
you can't draw very many conclusions from the number of tests that
are reported to fail. A crash will take out any concurrently-running
tests, so there's already some variability depending on whether any
concurrent scripts manage to finish before the one that crashed.
Plus, there are likely to be follow-on "failures" from later tests
that expect earlier tests to have left specific database state behind,
which they didn't because they failed to finish.
Counting the number of actual core dumps might provide some useful
data about whether things are better or worse.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Regina Obe | 2021-03-12 20:52:33 | RE: BUG #16920: Can't compile PostGIS with MingW64 against PostgreSQL 14 head |
| Previous Message | Regina Obe | 2021-03-12 19:07:29 | RE: BUG #16920: Can't compile PostGIS with MingW64 against PostgreSQL 14 head |