|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||"Tom Turelinckx" <pgbf(at)twiska(dot)com>|
|Cc:||"Andres Freund" <andres(at)anarazel(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org|
|Subject:||Re: snapper vs. HEAD|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
"Tom Turelinckx" <pgbf(at)twiska(dot)com> writes:
> Tom Lane wrote:
>> Thanks! But it doesn't seem to have taken: snapper just did a new run
>> that still failed, and it still seems to be using -O2.
> Snapper did build using -O1 a few hours ago, but it failed the check stage very early with a different error:
> FATAL: null value in column "classid" of relation "pg_depend" violates not-null constraint
Ugh. Compiler bugs coming out of the woodwork?
Not sure what to suggest here. It certainly is useful to us to have
sparc buildfarm testing, but probably sparc64 would be more useful
than sparc32. (It looks like FreeBSD and OpenBSD have dropped sparc32
altogether, and NetBSD has bumped it to tier II status.) One idea
is to try -O0 ...
regards, tom lane
|Next Message||Tom Lane||2020-03-30 18:00:42||Re: fix for BUG #3720: wrong results at using ltree|
|Previous Message||Tom Lane||2020-03-30 17:40:31||Re: snapper vs. HEAD|