| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Peter Geoghegan <pg(at)heroku(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: brin regression test intermittent failures |
| Date: | 2015-05-26 02:45:50 |
| Message-ID: | 28157.1432608350@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> Peter Geoghegan <pg(at)heroku(dot)com> writes:
>> I meant to get around to looking into it, but FWIW I see BRIN-related
>> Valgrind issues. e.g.:
> Fixed, see 79f2b5d583e2e2a7; but AFAICS this has no real-world impact
> so it does not explain whatever is happening on chipmunk.
BTW, after some further trawling in the buildfarm logs, it seem that that
"no results for" failure mode has been seen *only* on chipmunk, where it's
happened in roughly half the runs since that particular test case went in.
So it's definitely platform-specific. It's less clear whether the test
case is bogus, or it's exposing a bug added elsewhere in db5f98ab4fa44bc5,
or the bug was pre-existing but not exposed by any older test case.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2015-05-26 03:04:31 | Re: POC: Cache data in GetSnapshotData() |
| Previous Message | Josh Berkus | 2015-05-26 02:15:30 | Re: Asynchronous DRAM Self-Refresh |