| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: fixing REL7_3_STABLE build issues |
| Date: | 2005-07-16 18:11:52 |
| Message-ID: | 42D94DE8.6030407@dunslane.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Tom Lane wrote:
>"Andrew Dunstan" <andrew(at)dunslane(dot)net> writes:
>
>
>>Note that because of the way the buildfarm script works, this failure was
>>masking the seg errno bogosity. Maybe I should reverse the test order to
>>make contrib before running and regression tests.
>>
>>
>
>Seems like that'd just mask a different set of failures.
>
>
Yeah. I think I'd be more concerned by core regression failures than
contrib build failures - especially as they are often likely to have
more far reaching consequences.
>Is it practical to teach the script to run the tests that depend only on
>what you were able to build? I guess reporting the results would get
>more complicated ...
>
>
>
Not easily. It's really not much more on the client side than an
automation layer over existing build and test infrastructure. The script
itself has very little intelligence.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-07-16 18:19:14 | Re: fixing REL7_3_STABLE build issues |
| Previous Message | Tom Lane | 2005-07-16 18:06:07 | Re: [HACKERS] 4 pgcrypto regressions failures - 1 unsolved |