On 01/19/2015 09:53 AM, Tom Lane wrote:
Andrew Dunstan and...@dunslane.net writes:
But I'm wondering if we should look at using the tricks git-new-workdir
uses, setting up symlinks instead of a full clone. Then we'd have one
clone with a bunch of different work dirs. That plus a but of
On 1/19/15 1:07 PM, Andres Freund wrote:
On 2015-01-18 17:48:11 -0500, Tom Lane wrote:
One of the biggest causes of buildfarm run failures is out of disk
space. That's not just because people are running buildfarm critters
on small slow machines; it's because make check-world is an enormous
On 01/19/2015 12:28 AM, Tom Lane wrote:
An alternative would be to remove the pgsql directory at the end of the
run and thus do a complete fresh checkout each run. As you say it would
cost some time but save some space. At least it would be doable as an
option, not sure I'd want to make it
Andrew Dunstan and...@dunslane.net writes:
But I'm wondering if we should look at using the tricks git-new-workdir
uses, setting up symlinks instead of a full clone. Then we'd have one
clone with a bunch of different work dirs. That plus a but of explicitly
done garbage collection and
On 01/19/2015 09:53 AM, Tom Lane wrote:
Andrew Dunstan and...@dunslane.net writes:
But I'm wondering if we should look at using the tricks git-new-workdir
uses, setting up symlinks instead of a full clone. Then we'd have one
clone with a bunch of different work dirs. That plus a but of
Andrew Dunstan and...@dunslane.net writes:
On 01/18/2015 09:20 PM, Tom Lane wrote:
What I see on dromedary, which has been around a bit less than a year,
is that the at-rest space consumption for all 6 active branches is
2.4G even though a single copy of the git repo is just over 400MB:
$ du
On 01/18/2015 09:20 PM, Tom Lane wrote:
Andrew Dunstan and...@dunslane.net writes:
On 01/18/2015 05:48 PM, Tom Lane wrote:
One of the biggest causes of buildfarm run failures is out of disk
space. That's not just because people are running buildfarm critters
on small slow machines; it's
Andrew Dunstan and...@dunslane.net writes:
On 01/18/2015 05:48 PM, Tom Lane wrote:
One of the biggest causes of buildfarm run failures is out of disk
space. That's not just because people are running buildfarm critters
on small slow machines; it's because make check-world is an enormous
On 01/18/2015 05:48 PM, Tom Lane wrote:
One of the biggest causes of buildfarm run failures is out of disk
space. That's not just because people are running buildfarm critters
on small slow machines; it's because make check-world is an enormous
space hog. Some numbers from current HEAD:
On Mon, Jan 19, 2015 at 7:48 AM, Tom Lane t...@sss.pgh.pa.us wrote:
To make things better in the buildfarm, we'd have to back-patch this into
all active branches, but I don't see any big problem with doing so.
Any objections?
Back-patching sounds like a good idea to me. At least this will allow
One of the biggest causes of buildfarm run failures is out of disk
space. That's not just because people are running buildfarm critters
on small slow machines; it's because make check-world is an enormous
space hog. Some numbers from current HEAD:
clean source tree: 120MB
built
11 matches
Mail list logo