This is a discussion on buildfarm failures in ECPG-Check within the pgsql Hackers forums, part of the PostgreSQL category; --> It looks like something broke the ECPG-Check recently. A number of buildfarm members are failing. On Tue, 3 Oct ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| It looks like something broke the ECPG-Check recently. A number of buildfarm members are failing. On Tue, 3 Oct 2006, PG Build Farm wrote: > > > The PGBuildfarm member mongoose had the following event on branch HEAD: > > Failed at Stage: ECPG-Check > > The snapshot timestamp for the build that triggered this notification is: 2006-10-03 22:30:01 > > The specs of this machine are: > OS: Gentoo / 1.6.14 > Arch: i686 > Comp: icc / 9.0.032 > > For more information, see http://www.pgbuildfarm.org/cgi-bin/s...ngoose&br=HEAD > > -- Lewis's Law of Travel: The first piece of luggage out of the chute doesn't belong to anyone, ever. ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org |
| ||||
| Jeremy Drake <pgsql@jdrake.com> writes: > It looks like something broke the ECPG-Check recently. A number of > buildfarm members are failing. Looks like blow-back from the recent change in default GUC parameters. However, I think "update the expected output" is the wrong answer, because what we are looking at here is evidence that the ecpg checks will fail anyway against an installed system with nondefault settings. That test needs to be modified so that it doesn't depend on the value of any GUC parameter that it hasn't set for itself. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings |