Re: Sending out a request for more buildfarm animals? - Mailing list pgsql-hackers

From Tomas Vondra
Subject Re: Sending out a request for more buildfarm animals?
Date
Msg-id 53A89C7C.3080706@fuzzy.cz
Whole thread Raw
In response to Re: Sending out a request for more buildfarm animals?  (Tomas Vondra <tv@fuzzy.cz>)
List pgsql-hackers
On 15.5.2014 00:41, Tomas Vondra wrote:
> On 13.5.2014 20:42, Tomas Vondra wrote:
>> On 10.5.2014 20:21, Tomas Vondra wrote:
>>> On 9.5.2014 00:47, Tomas Vondra wrote:
>>>
>>> And I've requested 6 more animals - two for each compiler. One set for
>>> tests with basic CLOBBER, one set for recursive CLOBBER.
>>
>> Can someone please approve the animals I've requested a few days ago?
>> I'm already running the clobber tests with '--nosend --nostatus' and
>> it's already reporting some errors. Would be nice to get it to the
>> buildfarm.
> 
> So the new animals:
> 
> CLOBBER_CACHE_ALWAYS (+ others)
>  markhor  gcc
>  tick     clang/llvm
>  leech    icc
> 
> CLOBBER_CACHE_RECURSIVELY (+ others)
>  addax    gcc
>  mite     clang/llvm
>  barnacle icc
> 
> The builds trigger every hour, but it may take hours / days to get first
> results.

Just a quick update from barnacle, running the tests with recursive
CLOBBER. Right now the "top" shows this:

top - 23:16:55 up 43 days, 23:43, 1 user, load average: 3.16, 2.83, 2.61
Tasks:  36 total,   2 running,  34 sleeping,   0 stopped,   0 zombie
Cpu(s): 75.7%us, 7.6%sy, 0.0%ni, 16.4%id, 0.2%wa, 0.0%hi, 0.0%si, 0.0%st
Mem:   8059116k total,  7108540k used,   950576k free,   554060k buffers
Swap:  8388600k total,     1600k used,  8387000k free,  4809468k cached
 PID %CPU   TIME+  COMMAND7916 99.7 45373:24 postgres: pgbuild regression [local] CREATE INDEX 426 33.9  0:01.02
postgres:autovacuum worker process   regression7871  0.3  0:10.79 postgres: wal writer process   1  0.0  0:00.09
/sbin/init

So, it's running for >1 month without a crash (or obvious memory leaks).
Good ;-)

Anyway, I've been checking the animal regularly and I've seen the
'CREATE INDEX' for a very long time (at least 2 weeks, I guess). Sadly
there's no timestamp in log_line_prefix, so it's difficult to say
exactly which commands took the longest, but the last two commands
logged in postmaster.log are

[537ddad8.1eec:6] LOG:  statement: CREATE UNIQUE INDEX
test_replica_identity_keyab_key ON test_replica_identity (keya, keyb);
[537ddad8.1eec:7] LOG:  statement: CREATE UNIQUE INDEX
test_replica_identity_nonkey ON test_replica_identity (keya, nonkey);

regards
Tomas



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: [REVIEW] psql tab completion for DROP TRIGGER/RULE and ALTER TABLE ... DISABLE/ENABLE
Next
From: John Lumby
Date:
Subject: Re: Extended Prefetching using Asynchronous IO - proposal and patch