| From: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
|---|---|
| To: | <ler(at)lerctr(dot)org> |
| Cc: | <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: Going for 'all green' buildfarm results |
| Date: | 2006-06-02 11:22:23 |
| Message-ID: | 3895.24.211.165.134.1149247343.squirrel@www.dunslane.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Larry Rosenman said:
> Tom Lane wrote:
>> I've been making another pass over getting rid of buildfarm failures.
>> The remaining ones I see at the moment are:
>>
>> firefly HEAD: intermittent failures in the stats test. We seem to
>> have fixed every other platform back in January, but not this one.
>>
>>
>> firefly 7.4: dblink test fails, with what looks like an rpath problem.
>> Another one that we fixed awhile ago, and the fix worked on every
>> platform but this one.
>>
>> firefly 7.3: trivial regression diffs; we could install variant
>> comparison files if anyone cared.
>>
>>
>> Firefly is obviously the outlier here. I dunno if anyone cares
>> enough about SCO to spend time investigating it (I don't). Most of
>> the others just need a little bit of attention from the machine
>> owner.
>
> If I generate fixes for firefly (I'm the owner), would they have a
> prayer Of being applied?
>
Sure, although I wouldn't bother with 7.3 - just take 7.3 out of firefly's
build schedule. That's not carte blanche on fixes, of course - we'd have to
see them.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2006-06-02 12:16:46 | Re: Going for "all green" buildfarm results |
| Previous Message | Andrew Dunstan | 2006-06-02 11:18:24 | Re: 'CVS-Unknown' buildfarm failures? |