From: Willem Jan Withagen <wjw@digiware.nl>
To: ceph-devel@vger.kernel.org
Subject: Jenkins error in running tests ....
Date: Tue, 9 Feb 2016 10:25:53 +0100 [thread overview]
Message-ID: <56B9B0A1.6090807@digiware.nl> (raw)
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....
--WjW
next reply other threads:[~2016-02-09 9:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 9:25 Willem Jan Withagen [this message]
2016-02-10 11:58 ` Jenkins error in running tests kefu chai
2016-02-10 12:04 ` Willem Jan Withagen
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=56B9B0A1.6090807@digiware.nl \
--to=wjw@digiware.nl \
--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.