From: Mykola Golub <mgolub@mirantis.com>
To: Willem Jan Withagen <wjw@digiware.nl>
Cc: "Xinze Chi (信泽)" <xmdxcxz@gmail.com>,
"Ceph Development" <ceph-devel@vger.kernel.org>
Subject: Re: FreeBSD Building and Testing
Date: Wed, 6 Jan 2016 09:51:46 +0200 [thread overview]
Message-ID: <20160106075144.GA3402@gmail.com> (raw)
In-Reply-To: <568168F0.2060605@digiware.nl>
On Mon, Dec 28, 2015 at 05:53:04PM +0100, Willem Jan Withagen wrote:
> Hi,
>
> Can somebody try to help me and explain why
>
> in test: Func: test/mon/osd-crash
> Func: TEST_crush_reject_empty started
>
> Fails with a python error which sort of startles me:
> test/mon/osd-crush.sh:227: TEST_crush_reject_empty: local
> empty_map=testdir/osd-crush/empty_map
> test/mon/osd-crush.sh:228: TEST_crush_reject_empty: :
> test/mon/osd-crush.sh:229: TEST_crush_reject_empty: ./crushtool -c
> testdir/osd-crush/empty_map.txt -o testdir/osd-crush/empty_map.m
> ap
> test/mon/osd-crush.sh:230: TEST_crush_reject_empty: expect_failure
> testdir/osd-crush 'Error EINVAL' ./ceph osd setcrushmap -i testd
> ir/osd-crush/empty_map.map
> ../qa/workunits/ceph-helpers.sh:1171: expect_failure: local
> dir=testdir/osd-crush
> ../qa/workunits/ceph-helpers.sh:1172: expect_failure: shift
> ../qa/workunits/ceph-helpers.sh:1173: expect_failure: local 'expected=Error
> EINVAL'
> ../qa/workunits/ceph-helpers.sh:1174: expect_failure: shift
> ../qa/workunits/ceph-helpers.sh:1175: expect_failure: local success
> ../qa/workunits/ceph-helpers.sh:1176: expect_failure: pwd
> ../qa/workunits/ceph-helpers.sh:1177: expect_failure: printenv
> ../qa/workunits/ceph-helpers.sh:1178: expect_failure: echo ./ceph osd
> setcrushmap -i testdir/osd-crush/empty_map.map
> ../qa/workunits/ceph-helpers.sh:1180: expect_failure: ./ceph osd
> setcrushmap -i testdir/osd-crush/empty_map.map
> *** DEVELOPER MODE: setting PATH, PYTHONPATH and LD_LIBRARY_PATH ***
> Traceback (most recent call last):
> File "./ceph", line 936, in <module>
> retval = main()
> File "./ceph", line 874, in main
> sigdict, inbuf, verbose)
> File "./ceph", line 457, in new_style_command
> inbuf=inbuf)
> File "/usr/srcs/Ceph/wip-freebsd-wjw/ceph/src/pybind/ceph_argparse.py",
> line 1208, in json_command
> raise RuntimeError('"{0}": exception {1}'.format(argdict, e))
> RuntimeError: "{'prefix': u'osd setcrushmap'}": exception "['{"prefix": "osd
> setcrushmap"}']": exception 'utf8' codec can't decode b
> yte 0x86 in position 56: invalid start byte
>
> Which is certainly not the type of error expected.
> But it is hard to detect any 0x86 in the arguments.
Are you able to reproduce this problem manually? I.e. in src dir, start the
cluster using vstart.sh:
./vstart.sh -n
Check it is running:
./ceph -s
Repeat the test:
truncate -s 0 empty_map.txt
./crushtool -c empty_map.txt -o empty_map.map
./ceph osd setcrushmap -i empty_map.map
Expected output:
"Error EINVAL: Failed crushmap test: ./crushtool: exit status: 1"
--
Mykola Golub
next prev parent reply other threads:[~2016-01-06 7:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-20 16:10 FreeBSD Building and Testing Willem Jan Withagen
2015-12-21 0:45 ` Xinze Chi (信泽)
[not found] ` <CANE=7sU9QPH2uUS8A4xhPQ1j+jR6Fi88=PVvLRGEhzt2cmOceg@mail.gmail.com>
2015-12-21 1:16 ` Fwd: " Xinze Chi (信泽)
2015-12-21 20:14 ` Willem Jan Withagen
2015-12-28 16:53 ` Willem Jan Withagen
2016-01-05 18:23 ` Gregory Farnum
2016-01-06 10:21 ` Willem Jan Withagen
2016-01-06 7:51 ` Mykola Golub [this message]
2016-01-06 10:16 ` Willem Jan Withagen
2016-01-06 12:41 ` Willem Jan Withagen
2015-12-21 23:40 ` Willem Jan Withagen
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=20160106075144.GA3402@gmail.com \
--to=mgolub@mirantis.com \
--cc=ceph-devel@vger.kernel.org \
--cc=wjw@digiware.nl \
--cc=xmdxcxz@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 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.