public inbox for [email protected]
help / color / mirror / Atom feedbuildfarm client release 4.18
3+ messages / 2 participants
[nested] [flat]
* buildfarm client release 4.18
@ 2016-10-12 00:24 Andrew Dunstan <[email protected]>
2016-10-12 00:51 ` Re: buildfarm client release 4.18 Tom Lane <[email protected]>
0 siblings, 1 reply; 3+ messages in thread
From: Andrew Dunstan @ 2016-10-12 00:24 UTC (permalink / raw)
To: PostgreSQL-development <[email protected]>; buildfarm-members
I have just released buildfarm client version 4.18.
In addition to some minor fixes, there are two significant changes:
* The client now makes a determined effort to clean up any left over
build artefacts from previous runs at the start of a run. It also
tries to clean away old socket files. That means that manual fixes
are much less likely to be required, if the script has crashed or
the machine has crashed or restarted.
* There is a new config parameter "wait_timeout", which defaults to
undefined. If it is set then any run that takes longer than the
specified number of seconds is aborted. That means that runs that
get stuck will time out, and the whole animal won't be stuck and
requiring manual intervention. My test animal has a setting of 3 *
3600, i.e. 3 hours. There is some possible danger in this, that we
might miss bugs that cause us to get stuck, so at least some animals
should not use this feature.
The release can be downloaded from:
<http://www.pgbuildfarm.org/downloads/releases/build-farm-4_18.tgz;
cheers
andrew
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: buildfarm client release 4.18
2016-10-12 00:24 buildfarm client release 4.18 Andrew Dunstan <[email protected]>
@ 2016-10-12 00:51 ` Tom Lane <[email protected]>
2016-10-12 02:34 ` Re: buildfarm client release 4.18 Andrew Dunstan <[email protected]>
0 siblings, 1 reply; 3+ messages in thread
From: Tom Lane @ 2016-10-12 00:51 UTC (permalink / raw)
To: Andrew Dunstan <[email protected]>; +Cc: buildfarm-members
Andrew Dunstan <[email protected]> writes:
> * There is a new config parameter "wait_timeout", which defaults to
> undefined. If it is set then any run that takes longer than the
> specified number of seconds is aborted. That means that runs that
> get stuck will time out, and the whole animal won't be stuck and
> requiring manual intervention. My test animal has a setting of 3 *
> 3600, i.e. 3 hours. There is some possible danger in this, that we
> might miss bugs that cause us to get stuck, so at least some animals
> should not use this feature.
Hm, do you mean that if the timeout is exceeded, it just shuts down and
doesn't report the failure? If there is a report I don't see how we'd
"miss" anything.
regards, tom lane
--
Sent via buildfarm-members mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/buildfarm-members
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: buildfarm client release 4.18
2016-10-12 00:24 buildfarm client release 4.18 Andrew Dunstan <[email protected]>
2016-10-12 00:51 ` Re: buildfarm client release 4.18 Tom Lane <[email protected]>
@ 2016-10-12 02:34 ` Andrew Dunstan <[email protected]>
0 siblings, 0 replies; 3+ messages in thread
From: Andrew Dunstan @ 2016-10-12 02:34 UTC (permalink / raw)
To: Tom Lane <[email protected]>; +Cc: buildfarm-members
On 10/11/2016 08:51 PM, Tom Lane wrote:
> Andrew Dunstan <[email protected]> writes:
>> * There is a new config parameter "wait_timeout", which defaults to
>> undefined. If it is set then any run that takes longer than the
>> specified number of seconds is aborted. That means that runs that
>> get stuck will time out, and the whole animal won't be stuck and
>> requiring manual intervention. My test animal has a setting of 3 *
>> 3600, i.e. 3 hours. There is some possible danger in this, that we
>> might miss bugs that cause us to get stuck, so at least some animals
>> should not use this feature.
> Hm, do you mean that if the timeout is exceeded, it just shuts down and
> doesn't report the failure? If there is a report I don't see how we'd
> "miss" anything.
>
>
Yeah, unfortunately. I can look at making it report something, not sure
exactly how much will be possible.
cheers
andrew
--
Sent via buildfarm-members mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/buildfarm-members
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2016-10-12 02:34 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2016-10-12 00:24 buildfarm client release 4.18 Andrew Dunstan <[email protected]>
2016-10-12 00:51 ` Tom Lane <[email protected]>
2016-10-12 02:34 ` Andrew Dunstan <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox