[lttng-dev] Running lttng-tools tests?
Christian Babeux
christian.babeux at efficios.com
Thu May 30 15:16:08 EDT 2013
Hi Daniel,
> After installing lttng-tools (2.2.0-rc2) in /usr/src, I tried this:
>
> $ cd /usr/src/lttng-tools-2.2.0-rc2/tests
> $ ./run.sh unit_tests
This is indeed the right way to run the tests. Usually I run those in
the source tree _before_ installation e.g.:
[...]
make
cd lttng-tools/tests
./run.sh unit_tests
[...]
Or you can run the make check target after building:
[...]
./configure
make
make check
[...]
Perhaps there is an issue when the tests are installed? Make sure the
tests binaries are properly compiled and are present in the
installation paths. If not, we should remove any tests scripts/program
installation when issuing 'make install'...
Thanks,
Christian
On Thu, May 30, 2013 at 2:59 PM, Thibault, Daniel
<Daniel.Thibault at drdc-rddc.gc.ca> wrote:
> After installing lttng-tools (2.2.0-rc2) in /usr/src, I tried this:
>
> $ cd /usr/src/lttng-tools-2.2.0-rc2/tests
> $ ./run.sh unit_tests
>
> And I got this:
>
> unit/test_kernel_data .............. Dubious, test returned 1 (wstat 256, 0x100)
> No subtests run
> unit/test_session .................. Dubious, test returned 1 (wstat 256, 0x100)
> No subtests run
> unit/test_uri ...................... Dubious, test returned 1 (wstat 256, 0x100)
> No subtests run
> unit/test_ust_data ................. Dubious, test returned 1 (wstat 256, 0x100)
> No subtests run
> unit/test_utils_parse_size_suffix .. Dubious, test returned 1 (wstat 256, 0x100)
> No subtests run
>
> Test Summary Report
> -------------------
> unit/test_kernel_data (Wstat: 256 Tests: 0 Failed: 0)
> Non-zero exit status: 1
> Parse errors: No plan found in TAP output
> unit/test_session (Wstat: 256 Tests: 0 Failed: 0)
> Non-zero exit status: 1
> Parse errors: No plan found in TAP output
> unit/test_uri (Wstat: 256 Tests: 0 Failed: 0)
> Non-zero exit status: 1
> Parse errors: No plan found in TAP output
> unit/test_ust_data (Wstat: 256 Tests: 0 Failed: 0)
> Non-zero exit status: 1
> Parse errors: No plan found in TAP output
> unit/test_utils_parse_size_suffix (Wstat: 256 Tests: 0 Failed: 0)
> Non-zero exit status: 1
> Parse errors: No plan found in TAP output
> Files=5, Tests=0, 0 wallclock secs ( 0.03 usr 0.00 sys + 0.04 cusr 0.04 csys = 0.11 CPU)
> Result: FAIL
>
> There is no README in lttng-tools/tests (unlike lttng-ust, but sadly like userspace-rcu), and the script is laconic, so I can't be sure if this is a true failure (my installation works) or if I just ran the tests wrong. For userspace-rcu, I ran ' ./runtests.sh 2 2 10', but I got no PASS/FAIL evaluation so I'm not 100% sure the tests were a success.
>
> How are these tests supposed to be run?
>
> Daniel U. Thibault
> Protection des systèmes et contremesures (PSC) | Systems Protection & Countermeasures (SPC)
> Cyber sécurité pour les missions essentielles (CME) | Mission Critical Cyber Security (MCCS)
> R & D pour la défense Canada - Valcartier (RDDC Valcartier) | Defence R&D Canada - Valcartier (DRDC Valcartier)
> 2459 route de la Bravoure
> Québec QC G3J 1X5
> CANADA
> Vox : (418) 844-4000 x4245
> Fax : (418) 844-4538
> NAC : 918V QSDJ <http://www.travelgis.com/map.asp?addr=918V%20QSDJ>
> Gouvernement du Canada | Government of Canada
> <http://www.valcartier.drdc-rddc.gc.ca/>
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
More information about the lttng-dev
mailing list