From: Willem Jan Withagen <wjw@digiware.nl>
To: kefu chai <tchaikov@gmail.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Jenkins error in running tests ....
Date: Wed, 10 Feb 2016 13:04:13 +0100 [thread overview]
Message-ID: <56BB273D.2040007@digiware.nl> (raw)
In-Reply-To: <CAJE9aONSEzJVWe4Ows7oNrg403_ucT4vYdvCNEujGr74h7cYqw@mail.gmail.com>
On 10-2-2016 12:58, kefu chai wrote:
> On Tue, Feb 9, 2016 at 5:25 PM, Willem Jan Withagen <wjw@digiware.nl> wrote:
>> Hi,
>>
>> https://jenkins.ceph.com/job/ceph-pull-requests/1261/console
>>
>> .......
>> PASS: test/osd/osd-scrub-repair.sh
>> make[5]: execvp: /bin/sh: Argument list too long
>> make[5]: *** [test-suite.log] Error 127
>> make[5]: Leaving directory
>> `/home/jenkins-build/build/workspace/ceph-pull-requests/src'
>> make[4]: *** [check-TESTS] Error 2
>> make[4]: Leaving directory
>> `/home/jenkins-build/build/workspace/ceph-pull-requests/src'
>> make[3]: *** [check-am] Error 2
>>
>> I'm assuming that it is not something I did in my code.
>> But then again I've been proven wrong....
>
> Willem, seems you are not the only one having this failure in the
> jenkins run. i have
> the same error in
> https://jenkins.ceph.com/job/ceph-pull-requests/1294/console for
> my pull request of https://github.com/ceph/ceph/pull/7523 as well.
Problem is that I cannot reproduce it here. Atleast not thusfar.
And Jenkins has limitted debug possibilities.
So, i guess, it is a sort of catch-22, which needs to be solved by
people with more access to the platform.
--WjW
next prev parent reply other threads:[~2016-02-10 13:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 9:25 Jenkins error in running tests Willem Jan Withagen
2016-02-10 11:58 ` kefu chai
2016-02-10 12:04 ` Willem Jan Withagen [this message]
2016-02-10 14:17 ` 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=56BB273D.2040007@digiware.nl \
--to=wjw@digiware.nl \
--cc=ceph-devel@vger.kernel.org \
--cc=tchaikov@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox