After upgrading some of my buildfarm members to the latest version of
the buildfarm script both OpenBSD boxes startet to fail the ECPG
regression tests:

http://www.pgbuildfarm.org/cgi-bin/s...-05%2002:35:02

and

http://www.pgbuildfarm.org/cgi-bin/s...-04%2023:50:05



Stefan

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

Michael Meskes wrote:
> On Tue, Sep 05, 2006 at 08:00:12AM +0200, Stefan Kaltenbrunner wrote:
>> After upgrading some of my buildfarm members to the latest version of
>> the buildfarm script both OpenBSD boxes startet to fail the ECPG
>> regression tests:
>> ...
>
> complex/test2 gets a segmentation fault on both machines. Could you try
> running it under gdb to see where it segfaults? I will try to get a hand
> on an OpenBSD machine myself, too

will try to get a backtrace soon - if you are trying to do your own
testing keep in mind that both boxes of mine do run with special
malloc-settings (as in FGJZ) as discussed in:

http://archives.postgresql.org/pgsql...6/msg00817.php

while I'm not sure yet that those are causing the errors to show up it
seems quite likely since they tend to catch hidden memory allocation errors.


Stefan

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

> >> After upgrading some of my buildfarm members to the latest version of
> >> the buildfarm script both OpenBSD boxes startet to fail the ECPG
> >> regression tests:
> >> ...
> >
> > complex/test2 gets a segmentation fault on both machines. Could you try
> > running it under gdb to see where it segfaults? I will try to get a hand
> > on an OpenBSD machine myself, too
>
> will try to get a backtrace soon - if you are trying to do your own
> testing keep in mind that both boxes of mine do run with special
> malloc-settings (as in FGJZ) as discussed in:
>
> http://archives.postgresql.org/pgsql...6/msg00817.php
>
> while I'm not sure yet that those are causing the errors to show up it
> seems quite likely since they tend to catch hidden memory allocation errors.

Hi,

I've just upgraded guppy, the only other OpenBSD machine that builds
head to the latest buildfarm version.

I don't have any special malloc settings. When guppy finishes, we will
see what happens.

Bye, Chris.


--

Chris Mair
http://www.1006.org


---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

Michael Meskes wrote:
> On Tue, Sep 05, 2006 at 01:08:48PM +0200, Stefan Kaltenbrunner wrote:
>> FYI: complex/test2 fails on lionfish (my linux/mipsel box) too:
>>
>> http://www.pgbuildfarm.org/cgi-bin/s...-05%2005:30:07
>
> This needs some debugging. The output difference comes from an indicator
> not correctly set/evaluated. To get more infos I need to get access to
> such a machine.

hmm I might be able to arrange access to lionfish - but that box is slow
(it needs between 5 and 6 hours to finish a buildfarm run).


Stefan

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

> > will try to get a backtrace soon - if you are trying to do your own
> > testing keep in mind that both boxes of mine do run with special
> > malloc-settings (as in FGJZ) as discussed in:
> >
> > http://archives.postgresql.org/pgsql...6/msg00817.php
> >
> > while I'm not sure yet that those are causing the errors to show up it
> > seems quite likely since they tend to catch hidden memory allocation errors.
>
> Hi,
>
> I've just upgraded guppy, the only other OpenBSD machine that builds
> head to the latest buildfarm version.
>
> I don't have any special malloc settings. When guppy finishes, we will
> see what happens.

Hi,

after a spurious run due to a config mistake after upgrading (sorry),
guppy just now completed a new run and also failed on "make ecpg check":

http://www.pgbuildfarm.org/cgi-bin/s...dt=2006-09-05%
2010:02:05

Michael, if you want shell access to guppy, just contact me privately.
Warning: guppy too, is somewhat dated (1:10 hours for the make step) :/

Bye, Chris.



--

Chris Mair
http://www.1006.org


---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

> Michael, if you want shell access to guppy, just contact me privately.
> Warning: guppy too, is somewhat dated (1:10 hours for the make step) :/

Michael,
did you receive my private mail yesterday?
(just want to make sure it wasn't blocked by an overzealous spam filter)

Bye, Chris.

--

Chris Mair
http://www.1006.org



---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org