From: Loic Dachary <loic@dachary.org>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: make check bot delays
Date: Thu, 15 Oct 2015 11:08:47 +0200 [thread overview]
Message-ID: <561F6D1F.30603@dachary.org> (raw)
In-Reply-To: <561ED1D6.7060905@dachary.org>
[-- Attachment #1: Type: text/plain, Size: 1317 bytes --]
Hi,
TL;DR: the make check bot is fixed (no more delays) but only keeps the last 30 runs
It looks like the cause of the jenkins delays was the number of run kept in the archives (set to 300). Lowering it down to 30 have jenkins back to running with no delay between jobs (as opposed to using 100% of one core during 10 minutes between two jobs, apparently to do things on the archived runs).
What I can't really explain is that it also kept 300 jobs two month ago and that was no issue. What changed in between... I have no clue.
The bot is catching up.
Cheers
On 15/10/2015 00:06, Loic Dachary wrote:
> Hi,
>
> TL;DR: the jenkins instance running make check bot hangs daily, looking for a solution
>
> In the past two weeks the make check bot has experienced troubles for which I've been unable to find a cause. The same jenkins instance running it for the past nine month now freezes at random times. Nothing in the logs, no error message: either the page or the slave are just doing nothing no matter what. The only reliable solution seems to be a restart of jenkins (killing the process since even restart blocks).
>
> Maybe it's time for the make check bot to run via teuthology instead of jenkins.
>
> Thanks for your patience
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-10-15 9:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 22:06 make check bot delays Loic Dachary
2015-10-15 9:08 ` Loic Dachary [this message]
2015-10-15 9:45 ` Dałek, Piotr
2015-10-15 9:55 ` Loic Dachary
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=561F6D1F.30603@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.