Paul Jungwirth <pj@illuminatedcomputing.com> writes:
> I can't find a regression.diffs in the second link. Is there one? I can't tell if it's the same
> failure as in the first link as not.
It is the same, but the diff is buried in some other file,
probably regress_log_027_stream_regress.
> I ran installcheck-parallel on my own machine continuously over night and haven't been able to
> reproduce this yet. How many cases have appeared on the build farm? More than these two? And just to
> confirm: they are only since committing 1772d554b0?
I've only noticed the two, but I did not mount an aggressive search.
It's possible that there were failures before 1772d554b0, since I
now see that the diff is in a test case that is older than that.
> The infrequent failure made me suspect a memory error. It's hard to come up with explanations.
Same error on two different machines makes it hard to credit hardware
glitches, if that's what you mean. I could believe a bad pointer
accessing unpredictable memory, but perhaps valgrind would catch that.
regards, tom lane
