[lttng-dev] babeltrace test failures on some architectures
Jon Bernard
jbernard at debian.org
Thu Jun 12 23:51:17 EDT 2014
* Jérémie Galarneau <jeremie.galarneau at efficios.com> wrote:
> The build logs only seem to contain the "prove" output (invoked by run.sh).
>
> Could you run tests/bin/test_trace_read and
> tests/lib/test_seek_empty_packet on armel and sparc? The output of
> both of these tests and the coredumps (if any) should give me
> something to work with.
Here are the sparc results:
$ ./tests/bin/test_trace_read
1..17
./tests/bin/test_trace_read: line 34: 31489 Bus error $BABELTRACE_BIN ${path} > /dev/null 2>&1
not ok 1 - Run babeltrace with trace env-warning
# Failed test 'Run babeltrace with trace env-warning'
# in ./tests/bin/test_trace_read:main() at line 37.
./tests/bin/test_trace_read: line 34: 31508 Bus error $BABELTRACE_BIN ${path} > /dev/null 2>&1
not ok 2 - Run babeltrace with trace lttng-modules-2.0-pre5
# Failed test 'Run babeltrace with trace lttng-modules-2.0-pre5'
# in ./tests/bin/test_trace_read:main() at line 37.
./tests/bin/test_trace_read: line 34: 31527 Bus error $BABELTRACE_BIN ${path} > /dev/null 2>&1
not ok 3 - Run babeltrace with trace sequence
# Failed test 'Run babeltrace with trace sequence'
# in ./tests/bin/test_trace_read:main() at line 37.
./tests/bin/test_trace_read: line 34: 31546 Bus error $BABELTRACE_BIN ${path} > /dev/null 2>&1
not ok 4 - Run babeltrace with trace smalltrace
# Failed test 'Run babeltrace with trace smalltrace'
# in ./tests/bin/test_trace_read:main() at line 37.
./tests/bin/test_trace_read: line 34: 31565 Bus error $BABELTRACE_BIN ${path} > /dev/null 2>&1
not ok 5 - Run babeltrace with trace succeed1
# Failed test 'Run babeltrace with trace succeed1'
# in ./tests/bin/test_trace_read:main() at line 37.
./tests/bin/test_trace_read: line 34: 31584 Bus error $BABELTRACE_BIN ${path} > /dev/null 2>&1
not ok 6 - Run babeltrace with trace succeed2
# Failed test 'Run babeltrace with trace succeed2'
# in ./tests/bin/test_trace_read:main() at line 37.
./tests/bin/test_trace_read: line 34: 31603 Bus error $BABELTRACE_BIN ${path} > /dev/null 2>&1
not ok 7 - Run babeltrace with trace succeed3
# Failed test 'Run babeltrace with trace succeed3'
# in ./tests/bin/test_trace_read:main() at line 37.
./tests/bin/test_trace_read: line 34: 31622 Bus error $BABELTRACE_BIN ${path} > /dev/null 2>&1
not ok 8 - Run babeltrace with trace succeed4
# Failed test 'Run babeltrace with trace succeed4'
# in ./tests/bin/test_trace_read:main() at line 37.
./tests/bin/test_trace_read: line 34: 31641 Bus error $BABELTRACE_BIN ${path} > /dev/null 2>&1
not ok 9 - Run babeltrace with trace test
# Failed test 'Run babeltrace with trace test'
# in ./tests/bin/test_trace_read:main() at line 37.
./tests/bin/test_trace_read: line 34: 31660 Bus error $BABELTRACE_BIN ${path} > /dev/null 2>&1
not ok 10 - Run babeltrace with trace warnings
# Failed test 'Run babeltrace with trace warnings'
# in ./tests/bin/test_trace_read:main() at line 37.
./tests/bin/test_trace_read: line 34: 31679 Bus error $BABELTRACE_BIN ${path} > /dev/null 2>&1
not ok 11 - Run babeltrace with trace wk-heartbeat-u
# Failed test 'Run babeltrace with trace wk-heartbeat-u'
# in ./tests/bin/test_trace_read:main() at line 37.
./tests/bin/test_trace_read: line 40: 31698 Bus error $BABELTRACE_BIN ${path} > /dev/null 2>&1
ok 12 - Run babeltrace with invalid trace fail1
./tests/bin/test_trace_read: line 40: 31713 Bus error $BABELTRACE_BIN ${path} > /dev/null 2>&1
ok 13 - Run babeltrace with invalid trace fail2
./tests/bin/test_trace_read: line 40: 31728 Bus error $BABELTRACE_BIN ${path} > /dev/null 2>&1
ok 14 - Run babeltrace with invalid trace integer-range
ok 15 - Run babeltrace with invalid trace lttng-modules-2.0-pre1
ok 16 - Run babeltrace with invalid trace packet-based-metadata
./tests/bin/test_trace_read: line 40: 31773 Bus error $BABELTRACE_BIN ${path} > /dev/null 2>&1
ok 17 - Run babeltrace with invalid trace smalltrace
# Looks like you failed 11 tests of 17.
$ ./tests/lib/test_seek_empty_packet
1..29
Bus error
I'll gather the arm results tomorrow.
--
Jon
More information about the lttng-dev
mailing list