From 2de206d6b209e5e3b518f38c9991e4434940f72e Mon Sep 17 00:00:00 2001 From: Wenji Huang Date: Tue, 8 Sep 2009 18:38:14 -0400 Subject: PR10604: check availability for example test cases * testsuite/systemtap.examples/check.exp: Handle with test_support. * testsuite/systemtap.examples/io/iostat-scsi.meta: Add meta-tag test_support. * testsuite/systemtap.examples/memory/mmanonpage.meta: Ditto. * testsuite/systemtap.examples/memory/mmfilepage.meta: Ditto. * testsuite/systemtap.examples/memory/mmreclaim.meta: Ditto. * testsuite/systemtap.examples/memory/mmwriteback.meta: Ditto. * testsuite/systemtap.examples/network/autofs4.meta: Ditto. * testsuite/systemtap.examples/network/dropwatch.meta: Ditto. * testsuite/systemtap.examples/process/schedtimes.meta: Ditto. --- testsuite/systemtap.examples/memory/mmwriteback.meta | 1 + 1 file changed, 1 insertion(+) (limited to 'testsuite/systemtap.examples/memory/mmwriteback.meta') diff --git a/testsuite/systemtap.examples/memory/mmwriteback.meta b/testsuite/systemtap.examples/memory/mmwriteback.meta index aab0f910..00a68827 100644 --- a/testsuite/systemtap.examples/memory/mmwriteback.meta +++ b/testsuite/systemtap.examples/memory/mmwriteback.meta @@ -9,5 +9,6 @@ exit: user-controlled output: sorted-list scope: system-wide description: The mmwriteback.stp script uses the virtual memory tracepoints available in some kernels to report all of the file writebacks that occur form kupdate, pdflush and kjournald while the script is running. Its useful in determining where writes are coming from on a supposedly idle system that is experiencing upexpected IO. +test_support: stap -l kernel.trace("mm_pdflush_bgwriteout"),kernel.trace("mm_pdflush_kupdate"),kernel.trace("mm_pagereclaim_pgout") test_check: stap -p4 mmwriteback.stp test_installcheck: stap mmwriteback.stp -c "sleep 1" -- cgit From 22ce80766c4f31a218da1694569523eb68737faf Mon Sep 17 00:00:00 2001 From: Mark Wielaard Date: Sun, 13 Sep 2009 23:57:42 +0200 Subject: Make check.exp not sleep so much in test_installcheck. A lot of time during the installcheck was spend just sleeping. Reduce the sleep time by at least one fifth. * testsuite/systemtap.examples/*/*meta: Reduct -c "sleep" time. --- testsuite/systemtap.examples/memory/mmwriteback.meta | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'testsuite/systemtap.examples/memory/mmwriteback.meta') diff --git a/testsuite/systemtap.examples/memory/mmwriteback.meta b/testsuite/systemtap.examples/memory/mmwriteback.meta index 00a68827..1ad4947c 100644 --- a/testsuite/systemtap.examples/memory/mmwriteback.meta +++ b/testsuite/systemtap.examples/memory/mmwriteback.meta @@ -11,4 +11,4 @@ scope: system-wide description: The mmwriteback.stp script uses the virtual memory tracepoints available in some kernels to report all of the file writebacks that occur form kupdate, pdflush and kjournald while the script is running. Its useful in determining where writes are coming from on a supposedly idle system that is experiencing upexpected IO. test_support: stap -l kernel.trace("mm_pdflush_bgwriteout"),kernel.trace("mm_pdflush_kupdate"),kernel.trace("mm_pagereclaim_pgout") test_check: stap -p4 mmwriteback.stp -test_installcheck: stap mmwriteback.stp -c "sleep 1" +test_installcheck: stap mmwriteback.stp -c "sleep 0.2" -- cgit