Bug 14390 - separate process.**.return tests and mark UNSUPPORTED
Summary: separate process.**.return tests and mark UNSUPPORTED
Status: RESOLVED FIXED
Alias: None
Product: systemtap
Classification: Unclassified
Component: testsuite (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-23 21:47 UTC by Josh Stone
Modified: 2013-01-29 18:24 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Josh Stone 2012-07-23 21:47:51 UTC
With the current inode-uprobes, we don't have any mechanism to do .return probes.  Many of our uprobes testsuite assume that .return always comes along for the ride, so we currently get many failures just due to missing .return.

As much as possible, we should split up uprobes tests that may work partly with and without .return probes, and then mark tests UNSUPPORTED where appropriate.
Comment 1 Mark Wielaard 2012-07-31 10:26:26 UTC
This is also affecting at least at_var.exp and global_var.exp which test various combinations of @var() with things like @entry() and so rely on being able to set return probes and check the results.
Comment 2 Frank Ch. Eigler 2013-01-29 18:24:14 UTC
commit 9c41fd et al.