summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJosh Stone <jistone@redhat.com>2009-04-01 17:01:53 -0700
committerJosh Stone <jistone@redhat.com>2009-04-01 17:01:53 -0700
commit1fd65aa57e608b544122b4aacdfae9cce6cb89dc (patch)
treede59c22259653063e276d035f2401e0265f0c304
parent055f682bed95348cabb20868d62c4e575b84d02a (diff)
downloadsystemtap-steved-1fd65aa57e608b544122b4aacdfae9cce6cb89dc.tar.gz
systemtap-steved-1fd65aa57e608b544122b4aacdfae9cce6cb89dc.tar.xz
systemtap-steved-1fd65aa57e608b544122b4aacdfae9cce6cb89dc.zip
Move testcase itrace3's warning into expect
As it was, the ATTENTION was causing expect mismatches even when the test worked fine. The warning is served just as well from the expect script before starting the test.
-rw-r--r--testsuite/systemtap.base/itrace.exp2
1 files changed, 1 insertions, 1 deletions
diff --git a/testsuite/systemtap.base/itrace.exp b/testsuite/systemtap.base/itrace.exp
index d330a337..504253fe 100644
--- a/testsuite/systemtap.base/itrace.exp
+++ b/testsuite/systemtap.base/itrace.exp
@@ -53,7 +53,6 @@ set itrace3_script {
probe begin
{
printf("systemtap starting probe\n")
- printf("ATTENTION: if arch_has_block_step is not defined for this arch, this testcase will fail\n")
}
probe process("%s").insn.block
{
@@ -126,6 +125,7 @@ if {$utrace_support_found == 0} {
} elseif {![installtest_p]} {
untested $TEST_NAME
} else {
+ send_log "ATTENTION: if arch_has_block_step is not defined for this arch, this testcase will fail\n"
set script [format $itrace3_script $exepath]
stap_run $TEST_NAME run_ls_5_sec $itrace3_script_output -e $script
}