Re: Missing info for buildfarm reports

From: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
To: <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: Missing info for buildfarm reports
Date: 2005-07-18 07:28:00
Message-ID: 1670.24.211.165.134.1121671680.squirrel@www.dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane said:
> I'm finding it a bit annoying that the buildfarm results pages will
> only show me what the program thinks I need to know. For example, to
> debug the current 7.4-branch dblink failures, it'd be awfully useful to
> compare the build logs of those systems to the same machines' logs for
> the not-broken 8.0 branch. But unless there's a magic back door
> somewhere, I can't see either of those logs.
>
> I think the ideal layout for the per-test-run pages would be the short
> configuration summary plus links to the individual log files --- all of
> them, no matter what the script thinks the outcome is.
>

We're ahead of you (just) :-) . This feature request was filed a few days
ago - see
http://pgfoundry.org/tracker/index.php?func=detail&aid=1000368&group_id=1000040&atid=241
It will take a little while though.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2005-07-18 12:20:25 Re: Constraint Exclusion (Partitioning) - Initial Review
Previous Message Tom Lane 2005-07-18 05:05:09 Buildfarm failure analysis: penguin on 7.4 branch