Prev: [HACKERS] dblink regression failure in HEAD
Next: explain.c: why trace PlanState and Plan trees separately?
From: Tom Lane on 12 Jul 2010 23:02
Itagaki Takahiro <itagaki.takahiro(a)gmail.com> writes:
> I found regression test for dblink in HEAD was failed on my machine.
> One buildfarm machine also reported the same failure.

What this looks like to me is that dblink.c doesn't contain the fix
that the new regression test is checking for.

pangolin is pulling from the git mirror, which I still don't trust
further than I can throw it. How about you?

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Alvaro Herrera on 12 Jul 2010 23:22
Excerpts from Tom Lane's message of lun jul 12 23:02:05 -0400 2010:

> pangolin is pulling from the git mirror, which I still don't trust
> further than I can throw it. How about you?

Easy enough to check -- just verify the $PostgreSQL$ tag in the file.

Oh wait ...

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Andrew Dunstan on 12 Jul 2010 23:32


Tom Lane wrote:
> Itagaki Takahiro <itagaki.takahiro(a)gmail.com> writes:
>
>> I found regression test for dblink in HEAD was failed on my machine.
>> One buildfarm machine also reported the same failure.
>>
>
> What this looks like to me is that dblink.c doesn't contain the fix
> that the new regression test is checking for.
>
> pangolin is pulling from the git mirror, which I still don't trust
> further than I can throw it. How about you?
>
>
>

There is something very odd about that machine. It started failing 5
days ago. Then it stopped, then it started again.

As for the git mirror, I can only speak for the mirror I maintain, which
is validated on every live branch every day against CVS, so far without
a hiccup, and has four of my buildfarm members happily building against
it (and possibly others).

cheers

andrew

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Tom Lane on 13 Jul 2010 00:25
Andrew Dunstan <andrew(a)dunslane.net> writes:
> Tom Lane wrote:
>> What this looks like to me is that dblink.c doesn't contain the fix
>> that the new regression test is checking for.
>>
>> pangolin is pulling from the git mirror, which I still don't trust
>> further than I can throw it. How about you?

> There is something very odd about that machine. It started failing 5
> days ago. Then it stopped, then it started again.

A few experiments later: I can reproduce the failure shown on pangolin
exactly if I revert the latest changes in sql/dblink.sql and
expected/dblink.out, while keeping dblink.c up to date. So I guessed
wrong on which file was out of sync, but I say confidently that this
is a repository sync problem.

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Stephen Frost on 13 Jul 2010 07:05
* Tom Lane (tgl(a)sss.pgh.pa.us) wrote:
> A few experiments later: I can reproduce the failure shown on pangolin
> exactly if I revert the latest changes in sql/dblink.sql and
> expected/dblink.out, while keeping dblink.c up to date. So I guessed
> wrong on which file was out of sync, but I say confidently that this
> is a repository sync problem.

I'll check with Scott on this, sorry, but it might be an issue with the
machine and not the repository. That's the box that he's been doing the
performance-farm work on and it's entirely possible soemthing got
screwed up there. Of course, it could also be a repository problem,
I'll find out.

Thanks,

Stephen
 |  Next  |  Last
Pages: 1 2
Prev: [HACKERS] dblink regression failure in HEAD
Next: explain.c: why trace PlanState and Plan trees separately?