This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug testsuite/18552] New: the dump_probe_aliases.exp test case has a failure because a syscall probe no longer exists


https://sourceware.org/bugzilla/show_bug.cgi?id=18552

            Bug ID: 18552
           Summary: the dump_probe_aliases.exp test case has a failure
                    because a syscall probe no longer exists
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: testsuite
          Assignee: systemtap at sourceware dot org
          Reporter: dsmith at redhat dot com
  Target Milestone: ---

The dump_probe_aliases test case output on all platforms looks like this:

====
Running ../../src/testsuite/systemtap.base/dump_probe_aliases.exp ...
PASS: dump_probe_aliases (got output of stap --dump-probe-aliases)
PASS: dump_probe_aliases (got output of stap -v --dump-probe-aliases)
PASS: dump_probe_aliases (oneshot in output)
PASS: dump_probe_aliases (vfs.read in output)
PASS: dump_probe_aliases (__syscall.lseek not in output)
PASS: dump_probe_aliases (oneshot in -v output)
PASS: dump_probe_aliases (vfs.read in -v output)
FAIL: dump_probe_aliases (__syscall.lseek in -v output)
testcase ../../src/testsuite/systemtap.base/dump_probe_aliases.exp completed in
1 seconds
====

That failure happens because the '__syscall.lseek' probe alias no longer
exists, not because 'stap -v --dump-probe-aliases' didn't output it.

-- 
You are receiving this mail because:
You are the assignee for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]