From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Trigger regression test output |
Date: | 2002-10-03 18:31:53 |
Message-ID: | 10898.1033669913@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> writes:
> So the regression tests weren't really testing the actually built module, so
> to speak. Is there a good reason to leave the NOTICE's in the expected
> regression output?
Yes: without them the test is less useful, because you're less certain
that what happened was what was supposed to happen.
> As to the way it's built, the regression tests are built in the RPMset to
> allow post-install (that is, post _RPM_ install) regression testing on
> machines without make or compilers.
Well, I'm about to commit a change that makes the default build of
contrib/spi have the correct NOTICE output, as of 7.3. You could make
the 7.2 RPMset do likewise if you wish.
One thing that confuses me though is that the build options have been
like this for a long time (at least since 7.1). Why haven't you seen
this problem before? Did you recently change the way the RPMs build
contrib?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2002-10-03 18:33:25 | Re: DROP COLUMN misbehaviour with multiple inheritance |
Previous Message | Adrian 'Dagurashibanipal' von Bidder | 2002-10-03 17:58:48 | Re: Oracle beats up on Open Source Database(s) ... and |