From: | Chris Mair <list(at)1006(dot)org> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: buildfarm stats |
Date: | 2006-07-05 19:34:43 |
Message-ID: | 1152128083.4457.7.camel@dell.home.lan |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> but it is about 2Gb of data, so just putting a dump cleaned of personal
> data somewhere isn't really an option.
>
> I could arrange a dump without the diagnostics, in these 2 tables:
>
> system: < name | operating_system | os_version | compiler |
> compiler_version | architecture >
> build: < name | snapshot | stage | branch | build_flags >
>
> (stage in the latter table is OK on success or the name of the stage
> that failed otherwise).
>
>
> But what do you want it for? And do you want it one-off or continuously?
Nothing important at all.
I'd just thought about a few interesting stats, like failures vs OS
(as the first poster said) or failures vs gcc version or timings vs.
arch / RAM or gcc version, etc. For the timings I guess there are
some timestamps embedded that might be extracted...
But I didn't really think about it, before posting (classic
mailing list syndrome ;)
Bye,
Chris.
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-07-05 19:40:41 | Re: buildfarm stats |
Previous Message | Phil Frost | 2006-07-05 18:51:09 | lastval exposes information that currval does not |