From: Loic Dachary <loic@dachary.org>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: make check bot paused
Date: Thu, 16 Apr 2015 19:22:00 +0200 [thread overview]
Message-ID: <552FEFB8.1040505@dachary.org> (raw)
In-Reply-To: <552E51A5.2060501@dachary.org>
[-- Attachment #1: Type: text/plain, Size: 1161 bytes --]
Hi,
It is back :-)
Cheers
On 15/04/2015 13:55, Loic Dachary wrote:
> Hi,
>
> The make check bot [1] that executes run-make-check.sh [2] on pull requests and reports results as comments [3] is experiencing problems. It may be a hardware issue and the bot is paused while the issue is investigated [4] to avoid sending confusing false negatives. In the meantime the run-make-check.sh [2] script can be run locally, before sending the pull request, to confirm the commits to be sent do not break them. It is expected to run in less than 15 minutes including compilation on a fast machine with a SSD (or RAM disk) and 8 cores and 32GB of RAM and may take up to two hours on a machine with a spinner and two cores.
>
> Thanks for your patience.
>
> Cheers
>
> [1] bot running on pull requests http://jenkins.ceph.dachary.org/job/ceph/
> [2] run-make-check.sh http://workbench.dachary.org/ceph/ceph/blob/master/run-make-check.sh
> [3] make check results example : https://github.com/ceph/ceph/pull/3946#issuecomment-93286840
> [4] possible RAM failure http://tracker.ceph.com/issues/11399
>
--
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-04-16 17:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 11:55 make check bot paused Loic Dachary
2015-04-16 17:22 ` Loic Dachary [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-04-28 22:40 Loic Dachary
2015-06-02 23:48 Loic Dachary
2015-06-05 23:32 ` Loic Dachary
2015-08-08 1:01 Loic Dachary
2015-08-08 11:50 ` Sage Weil
2015-08-10 13:22 ` Loic Dachary
2015-08-11 8:37 ` 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=552FEFB8.1040505@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.