XML option doesn't seem to work about libiscsi

[jonhermansen]

The XML file should be written to your current working directory into a file called 'CUnitAutomated-Results.xml'. Also, there's nothing that should prevent -v from being used with -x, though the CLI help text may read like they're mutually exclusive.

Just wondering, what version of CUnit are you using? From a package or installed/built from source? What does

ldd /usr/bin/iscsi-test-cu

output?

Platform may also be helpful, I can try to reproduce...

[mykaul]

[root@lg572 tmp]# ldd /usr/bin/iscsi-test-cu
/usr/bin/iscsi-test-cu:
linux-vdso.so.1 => (0x00007fff265ff000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007fd2037e9000)
libcunit.so.1 => /usr/lib64/libcunit.so.1 (0x00007fd2035da000)
libc.so.6 => /lib64/libc.so.6 (0x00007fd203246000)
libiscsi.so.3 => /usr/lib64/libiscsi.so.3 (0x00007fd203024000)
/lib64/ld-linux-x86-64.so.2 (0x00007fd2039f7000)

CentOS 6.5.

On Fedora20, still nothing. ldd:
yanivk@vd-yanivk:~/libiscsi/test-tool/.libs (master)> ldd ./iscsi-test-cu
linux-vdso.so.1 => (0x00007fff7e581000)
libdl.so.2 => /lib64/libdl.so.2 (0x00000030f0000000)
libcunit.so.1 => /usr/local/lib/libcunit.so.1 (0x00007ff3c9dfb000)
libc.so.6 => /lib64/libc.so.6 (0x00000030efc00000)
libiscsi.so.3 => /usr/local/lib/libiscsi.so.3 (0x00007ff3c9bd8000)
/lib64/ld-linux-x86-64.so.2 (0x00000030ef800000)

[sahlberg]

I use Ubuntu and the --xml option does produce these files.

$ libtool --mode=execute ldd test-tool/iscsi-test-cu
linux-vdso.so.1 => (0x00007fff79ad2000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fb553858000)
libcunit.so.1 => /usr/lib/libcunit.so.1 (0x00007fb55364c000)
libiscsi.so.3 => /data/sahlberg/libiscsi/lib/.libs/libiscsi.so.3
(0x00007fb553428000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fb553060000)
/lib64/ld-linux-x86-64.so.2 (0x00007fb553a88000)
libgcrypt.so.11 => /lib/x86_64-linux-gnu/libgcrypt.so.11
(0x00007fb552de2000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0
(0x00007fb552bdc000)

I have added an initial manpage for iscsi-test-cu and copied the text from
the README to the section for --xml.
Please look it over and suggest improvements. I do not use --xml myself so
I need help here to make the --xml section good.

regards
ronnie sahlberg

On Mon, Mar 24, 2014 at 2:06 PM, Yaniv Kaul [email protected]:

[root@lg572 tmp]# ldd /usr/bin/iscsi-test-cu
/usr/bin/iscsi-test-cu:
linux-vdso.so.1 => (0x00007fff265ff000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007fd2037e9000)
libcunit.so.1 => /usr/lib64/libcunit.so.1 (0x00007fd2035da000)
libc.so.6 => /lib64/libc.so.6 (0x00007fd203246000)
libiscsi.so.3 => /usr/lib64/libiscsi.so.3 (0x00007fd203024000)
/lib64/ld-linux-x86-64.so.2 (0x00007fd2039f7000)

CentOS 6.5.

On Fedora20, still nothing. ldd:
yanivk@vd-yanivk:~/libiscsi/test-tool/.libs (master)> ldd ./iscsi-test-cu
linux-vdso.so.1 => (0x00007fff7e581000)
libdl.so.2 => /lib64/libdl.so.2 (0x00000030f0000000)
libcunit.so.1 => /usr/local/lib/libcunit.so.1 (0x00007ff3c9dfb000)
libc.so.6 => /lib64/libc.so.6 (0x00000030efc00000)
libiscsi.so.3 => /usr/local/lib/libiscsi.so.3 (0x00007ff3c9bd8000)
/lib64/ld-linux-x86-64.so.2 (0x00000030ef800000)

Reply to this email directly or view it on GitHubhttps://github.com//issues/100#issuecomment-38500988
.

[jonhermansen]

I think I see what the issue is. You are trying to get CUnit XML output but not running any tests. Running:

iscsi-test-cu --xml -l

won't run any tests... try removing the "-l" bit and provide an iscsi:// target URL.

[mykaul]

I suspect it also doesn't write results if it fails right away:
/usr/bin/iscsi-test-cu -i iqn.2007-10.com.github:sahlberg:libiscsi:iscsi-test -t ALL.Inquiry iscsi://10.205.31.6:3260/iqn.2008-05.com.xtremio:001e67594d7d/0 --xml

READCAPACITY10 command: failed with sense. SENSE KEY:ILLEGAL_REQUEST(5) ASCQ:LOGICAL_UNIT_NOT_SUPPORTED(0x2500)

No XML.

[mykaul]

Two more issues that are partly related, perhaps worthy of a different issue:

1. You can't run multiple tests in a single run: '-t X -t Y'.
2. Due to this, when running a single '-t' it creates an XML with a fixed name, unrelated to the test it ran. When running another one, it overwrites that XML. So the interim solution is to run the perl script - which does convert them to Junit XMLs with names based on their test (found out it creates a 'reports' directory under which it puts the XMLs - worth documenting?)
3. Need to see if Jenkins can handle multiple XMLs.

[sahlberg]

I will close this issue as the initial issue has been resolved.

I think the right thing to do here is to add a mechanism where you can specify multiple tests or glob patterns for the test suite. I.e. add support so you can do something like option 1, you list above.

I have opened issue #106 to add a mechanism to do this as a separate issue.

[sahlberg]

I will close this issue as the initial issue has been resolved.

I think the right thing to do here is to add a mechanism where you can specify multiple tests or glob patterns for the test suite. I.e. add support so you can do something like option 1, you list above.

I have opened issue #106 to add a mechanism to do this as a separate issue.

[sahlberg]

Please have a look at issue #106.

I have added basic support so you can specify a comma-separated list of
tests.

On Tue, Mar 25, 2014 at 2:02 AM, Yaniv Kaul [email protected]:

Two more issues that are partly related, perhaps worthy of a different
issue:

1. You can't run multiple tests in a single run: '-t X -t Y'.
2. Due to this, when running a single '-t' it creates an XML with a fixed
   name, unrelated to the test it ran. When running another one, it overwrites
   that XML. So the interim solution is to run the perl script - which does
   convert them to Junit XMLs with names based on their test (found out it
   creates a 'reports' directory under which it puts the XMLs - worth
   documenting?)
3. Need to see if Jenkins can handle multiple XMLs.

Reply to this email directly or view it on GitHubhttps://github.com//issues/100#issuecomment-38542648
.