Bug 733182
| Summary: | sdt.exp: too few lines of output, got 10, expected 11 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Han Pingtian <phan> |
| Component: | systemtap | Assignee: | Stan Cox <scox> |
| Status: | CLOSED ERRATA | QA Contact: | qe-baseos-tools-bugs |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.2 | CC: | czhang, fche, mjw, scox, syeghiay, wcohen |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | systemtap-1.6-4.el6 | Doc Type: | Bug Fix |
| Doc Text: |
Cause
Some systemtap testsuite sdt.exp ran tests with STAP_SDT_V2,
an older, obsolete mechanism. Applications should be built
with the newer STAP_SDT_V3 interface; there is little reason in include
these in the test results.
Consequence
On some architectures such as the ppc the tests using the
STAP_SDT_V2 interface would fail because of ambiguities between
numeric constants and register numbers.
Fix
The sdt.exp now mark the STAP_SDT_V2 that fail as XFAIL.
Result
The sdt.exp tests using STAP_SDT_V2 that fail are no
longer included in the FAIL results.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-12-06 15:18:36 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 748554 | ||
|
Description
Han Pingtian
2011-08-25 03:29:19 UTC
These are all related to -DEXPERIMENTAL_KPROBE_SDT; which is not the documented way to use static user probes but was an alternative implementation strategy we experimented with. This could be used on a system where uprobes isn't available; having said that, perhaps there is no longer a reason to keep this implementation around. The upstream patch '1fbbc4d3b4' XFAILS these failures. Just as for bug #733181, we can backport the testsuite-xfail patch if desired. The underlying problem with the obsolete sdt.h version is not practical to correct however, so CANTFIX that part. Opinions about whether the xfail path is worth doing? (In reply to comment #4) > Just as for bug #733181, we can backport the testsuite-xfail patch if desired. > The underlying problem with the obsolete sdt.h version is not practical to > correct however, so CANTFIX that part. Opinions about whether the xfail path > is worth doing? Yes, xfail will save us to check the error's reason. Thanks.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Cause
Some systemtap testsuite sdt.exp ran tests with -DEXPERIMENTAL_KPROBE_SDT,
an older, obsolete mechanism. No existing applications should be built
with this obsolete mechanism and there is little reason in include
these in the test results.
Consequence
On some architectures the tests using the
-DEXPERIMENTAL_KPROBE_SDT would fail.
Fix
The sdt.exp now mark the problematic -DEXPERIMENTAL_KPROBE_SDT
that fail as XFAIL.
Result
The sdt.exp tests using -DEXPERIMENTAL_KPROBE_SDT that fail are no
longer included in the FAIL results.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1,14 +1,14 @@
Cause
- Some systemtap testsuite sdt.exp ran tests with -DEXPERIMENTAL_KPROBE_SDT,
- an older, obsolete mechanism. No existing applications should be built
- with this obsolete mechanism and there is little reason in include
+ Some systemtap testsuite sdt.exp ran tests with STAP_SDT_V2,
+ an older, obsolete mechanism. Applications should be built
+ with the newer STAP_SDT_V3 interface; there is little reason in include
these in the test results.
Consequence
- On some architectures the tests using the
- -DEXPERIMENTAL_KPROBE_SDT would fail.
+ On some architectures such as the ppc the tests using the
+ STAP_SDT_V2 interface would fail because of ambiguities between
+ numeric constants and register numbers.
Fix
- The sdt.exp now mark the problematic -DEXPERIMENTAL_KPROBE_SDT
- that fail as XFAIL.
+ The sdt.exp now mark the STAP_SDT_V2 that fail as XFAIL.
Result
- The sdt.exp tests using -DEXPERIMENTAL_KPROBE_SDT that fail are no
+ The sdt.exp tests using STAP_SDT_V2 that fail are no
longer included in the FAIL results.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1517.html |