Open p5pRT opened 10 years ago
hi folks\,
(apologies if copy-paste was bad idea)
Ive prepared a patchset which lets us run all tests under linux's perf stat.
perf stat output is similar to that provided by valgrind --tool=cachegrind
but it is very cheap to invoke\, since it uses modern CPU performance measuring hardware.
heres a run on my athlon-64\, a less-than-bleading-edge desktop from 2009.
A hot new i7 or xeon or AMD chip probably has many more measurements available.
Performance counter stats for './perl base/cond.t':
2.077911 task-clock # 0.640 CPUs utilized
2 context-switches # 0.963 K/sec
1 cpu-migrations # 0.481 K/sec
519 page-faults # 0.250 M/sec
2\,753\,978 cycles # 1.325 GHz
1\,725\,265 stalled-cycles-frontend # 62.65% frontend cycles idle
2\,405\,122 stalled-cycles-backend # 87.33% backend cycles idle
3\,278\,429 instructions # 1.19 insns per cycle
# 0.73 stalled cycles per insn [52.13%]
\
\
0.003244748 seconds time elapsed
Because perf stat --repeat N also computes std-deviation for each measurement\,
this patch makes that feature available.
./perl TEST -v -lxperf=10 re/pat_rt_report.t
perf stat --repeat 10 -- ./perl -I.. -MTestInit re/pat_rt_report.t
./perl -I.. -MTestInit re/pat_rt_report.t
Performance counter stats for './perl -I.. -MTestInit re/pat_rt_report.t' (10 runs):
98.749506 task-clock # 0.001 CPUs utilized ( +- 23.68% )
68 context-switches # 0.686 K/sec ( +- 82.04% )
10 cpu-migrations # 0.097 K/sec ( +- 17.44% )
2\,956 page-faults # 0.030 M/sec ( +- 23.22% )
254\,477\,657 cycles # 2.577 GHz ( +- 26.02% ) [50.43%]
75\,556\,485 stalled-cycles-frontend # 29.69% frontend cycles idle ( +- 19.50% ) [50.93%]
62\,921\,965 stalled-cycles-backend # 24.73% backend cycles idle ( +- 25.21% ) [51.50%]
241\,522\,257 instructions # 0.95 insns per cycle
# 0.31 stalled cycles per insn ( +- 34.07% ) [50.96%]
53\,147\,072 branches # 538.201 M/sec ( +- 31.19% ) [50.18%]
2\,451\,318 branch-misses # 4.61% of all branches ( +- 11.32% ) [49.95%]
141.101988701 seconds time elapsed ( +- 99.91% )
I think theres some value in those stdev numbers\, likely showing that:
with this much noise\, you must discount any measured performance improvements accordingly.
0001-t-TEST-add-w-to-shebang-fix-a-used-once-warning.patch 0002-t-TEST-move-our-found-out-to-its-real-scope.patch 0003-t-TEST-failure-doesnt-need-to-use-defined.patch 0004-t-TEST-add-a-common-timestamp.patch 0005-t-TEST-comment-some-of-the-results-loop-vars.patch 0006-t-TEST-move-do_nothing-test-after-option-handling-co.patch 0007-t-TEST-add-lxperf-option-to-run-tests-under-linux-s-.patch 0008-t-TEST-simplify-results-processing-loop.-TAP13.1.patch 0009-t-TEST-change-timings-Storable-key-perf-times-a-bett.patch 0010-t-TEST-suppress-2-uninitialized-envars-under-make-te.patch 0011-t-TEST-RFC-start-to-separate-out-valgrind-test-suppo.patch
1 shows almost no fallout\, surprising it wasnt done before.
2\,4\,9 are self-corrections to old errs.
5 minor comments on vars\, mech\, true even wo further patches.
6 does option handling before $do_nothing returns\, so that harness
can enable test behavior -options it already has access to via the shared routines.
There is probly some clash-of-options that needs resolution
7 adds new -lxperf(.+) option and mechanism to wrap tests in "perf stat ... ./perl ... $testfile"
actually using --repeat 3 will break due to TAP 13 strict interpretation.
So its BOLD in adding something that would break if used (but its not by default)\,
8 fixup \<$results> processing loop code that squawks about --repeat 3 runs
3 did some pre-cleanup work to try to minimize this patch\, but 8 is still tricky.
8 is bold in even touching the fine-til-now code\,
and for fixing it for TEST\, but not for test_harness\, which passes the subtests
[16:16:24] ../cpan/Test-Harness/t/nested.t .................................... All 5 subtests passed
but finally fails\, like:
Parse errors: Plan (1..660) must be at the beginning or end of the TAP output Tests out of sequence. Found (1) but expected (661) Tests out of sequence. Found (2) but expected (662) Tests out of sequence. Found (3) but expected (663) Tests out of sequence. Found (4) but expected (664)
10 isnt recently tested but left in as todo
11 is BOLD in arguing that we could use require "test-feature"
in parts of TEST that do "developer-tests".
The valgrind specific code is a fitting case\,
its rarely run\, and by few individuals.
This could be taken as a reason to remove it entirely\,
but instead we could separate it out so its easier to review\,
enhance\, extend\, and make more useful.
Theres no reason why it should be written in a primitive style\,
thats for TEST's hotpath.
alrightee\, that should do it.
COPY PASTING FOR CASUAL REVIEW\, ATTACHING FOR SIMPLE BRANCH & APPLY TESTING
[jimc@groucho perl]$ cat test-perf.patch From 79eceb6119bd51361a0b399f896dfa868cd14e56 Mon Sep 17 00:00:00 2001 From: Jim Cromie \jim\.cromie@​gmail\.com Date: Fri\, 19 Oct 2012 13:22:39 -0600 Subject: [PATCH 01/11] t/TEST: add -w to shebang\, fix a used-once warning
Adding -w should be ok\, despite peculiar code style; it avoids require\, unlike "use strict". Added risk of perl brokenness seems vanishingly small. Fix one used-once warning thus exposed\, and one test in FileHandle.t surprised by t/TEST's new '-w' in the shebang.
lib/FileHandle.t | 2 +- t/TEST | 4 ++-- 2 files changed\, 3 insertions(+)\, 3 deletions(-)
1.8.3.1
From a9f81eefbc93277decccf9b956bb4ebd10552c19 Mon Sep 17 00:00:00 2001 From: Jim Cromie \jim\.cromie@​gmail\.com Date: Fri\, 19 Oct 2012 21:29:39 -0600 Subject: [PATCH 02/11] t/TEST: move our @found out to its real scope
commit c96083ea8213 added our @found inside sub _find_tests\, but testing with strict exposes probs:
$ perl -cw -Ilib -Mstrict t/TEST Variable "@found" is not imported at t/TEST line 198. Variable "@found" is not imported at t/TEST line 202. Global symbol "@found" requires explicit package name at t/TEST line 198. Global symbol "@found" requires explicit package name at t/TEST line 202.
No point in arguing\, hoist decl out to file scope.
t/TEST | 3 ++- 1 file changed\, 2 insertions(+)\, 1 deletion(-)
1.8.3.1
From ba22a3ed7d42620606f811c1a3ad5eb00c4d972a Mon Sep 17 00:00:00 2001 From: Jim Cromie \jim\.cromie@​gmail\.com Date: Sun\, 7 Oct 2012 11:10:16 -0600 Subject: [PATCH 03/11] t/TEST: $failure doesnt need to use defined
$failure handling in \<$results> processing loop does not need extra subtlety of defined-ness checks - just give it an initial (false) value\, and check for truth.
t/TEST | 14 ++++++-------- 1 file changed\, 6 insertions(+)\, 8 deletions(-)
1.8.3.1
From 8b42821106e92c87e47718373ded25c8b1e7fab2 Mon Sep 17 00:00:00 2001 From: Jim Cromie \jim\.cromie@​gmail\.com Date: Fri\, 19 Oct 2012 13:43:11 -0600 Subject: [PATCH 04/11] t/TEST: add a common timestamp
Commit 0978c4bed computed a timestamp string as part of an output filename\, make it available for others.
t/TEST | 10 +++++++--- 1 file changed\, 7 insertions(+)\, 3 deletions(-)
1.8.3.1
From 4ee55210d525327bf679462f0d2990f73b3253e1 Mon Sep 17 00:00:00 2001 From: Jim Cromie \jim\.cromie@​gmail\.com Date: Fri\, 19 Oct 2012 21:26:35 -0600 Subject: [PATCH 05/11] t/TEST: comment some of the \<$results> loop vars
Add comments to var declarations\, to help clarify loop operation.
t/TEST | 10 +++++----- 1 file changed\, 5 insertions(+)\, 5 deletions(-)
1.8.3.1
From d651d8c4685ed2c99e4892cbaad5cd2a49ab8619 Mon Sep 17 00:00:00 2001 From: Jim Cromie \jim\.cromie@​gmail\.com Date: Sat\, 16 Nov 2013 11:32:44 -0700 Subject: [PATCH 06/11] t/TEST: move do_nothing test after option-handling code
As explained in commit c537bcda1\, $do_nothing's purpose is to prevent TEST from actually running the tests\, so that it can be required by harness\, and its routines reused.
This patch moves TEST's $do_nothing check after its option-handling code\, allowing those options to be used to alter the behavior of the TEST subroutines when called by harness\, the same as when they're called from TEST::main.
TODO: With TEST's option handling done even for $do_nothing cases\, it consumes all options before harness sees them\, so harness options -v and -torture are broken. There are multiple ways to handle it\, all needing some consensus:
- harness does selective option scanning before requiring TEST. It could either consume its options or pass them thru once it handles them.
- both -v and -torture are implemented by TEST and harness\, and mean qualitatively the same thing. OTOH\, any consumers of the respective outputs may care about differences. Simply\, could rename one of each option to avoid the conflict.
- use of $TEST::verbose (or are namespaces also to be avoided?)
t/TEST | 9 ++++----- 1 file changed\, 4 insertions(+)\, 5 deletions(-)
1.8.3.1
From c30213f0fe6a3d2f452a86f82439fb85b8770e25 Mon Sep 17 00:00:00 2001 From: Jim Cromie \jim\.cromie@​gmail\.com Date: Sun\, 7 Oct 2012 20:22:08 -0600 Subject: [PATCH 07/11] t/TEST: add -lxperf option to run tests under linux's perf stat
With this patch\, TEST can run each test-script under linux's perf stat. Since previous patch honors options for $do_nothing / requires\, harness can use perf stat too.
t]$ ./perl -I../lib TEST -lxperf t]$ ./perl harness -lxperf
"perf stat" output is comparable to that of "valgrind --tool=cachegrind" but it takes very little extra CPU to run:
export TEST_OPTS=-lxperf time make test time make test -------------- -------------- real 25m41.122s real 26m30.719s user 18m28.773s user 18m43.286s sys 1m12.705s sys 1m33.398s
Given this small runtime cost\, porters might be inclined to use it and inspect the data. There may be some core regression tests that are useful for benchmarking purposes.
EXAMPLES:
Performance counter stats for './perl base/cond.t':
2.077911 task-clock # 0.640 CPUs utilized
2 context-switches # 0.963 K/sec
1 cpu-migrations # 0.481 K/sec
519 page-faults # 0.250 M/sec
2\,753\,978 cycles # 1.325 GHz
1\,725\,265 stalled-cycles-frontend # 62.65% frontend cycles idle
2\,405\,122 stalled-cycles-backend # 87.33% backend cycles idle
3\,278\,429 instructions # 1.19 insns per cycle
# 0.73 stalled cycles
per insn [52.13%]
\
0.003244748 seconds time elapsed
perf stat --repeat N also computes std-deviation for each measurement it does\, so this patch makes that feature available. Std-dev will tell us when performance differences are lost in the noise.
./perl TEST -v -lxperf=10 re/pat_rt_report.t perf stat --repeat 10 -- ./perl -I.. -MTestInit re/pat_rt_report.t ./perl -I.. -MTestInit re/pat_rt_report.t
Performance counter stats for './perl -I.. -MTestInit re/pat_rt_report.t' (10 runs):
98.749506 task-clock # 0.001 CPUs utilized ( +- 23.68% ) 68 context-switches # 0.686 K/sec ( +- 82.04% ) 10 cpu-migrations # 0.097 K/sec ( +- 17.44% ) 2\,956 page-faults # 0.030 M/sec ( +- 23.22% ) 254\,477\,657 cycles # 2.577 GHz ( +- 26.02% ) [50.43%] 75\,556\,485 stalled-cycles-frontend # 29.69% frontend cycles idle ( +- 19.50% ) [50.93%] 62\,921\,965 stalled-cycles-backend # 24.73% backend cycles idle ( +- 25.21% ) [51.50%] 241\,522\,257 instructions # 0.95 insns per cycle # 0.31 stalled cycles per insn ( +- 34.07% ) [50.96%] 53\,147\,072 branches # 538.201 M/sec ( +- 31.19% ) [50.18%] 2\,451\,318 branch-misses # 4.61% of all branches ( +- 11.32% ) [49.95%]
141.101988701 seconds time elapsed ( +- 99.91% )
The patch has 3 parts:
An addition to TEST:_cmd() which wraps the test invocation inside a "perf stat ..." as shown above\, using a %cmdwrap template.
Option-parsing code\, which handles several option forms: 1) -lxperf writes file "$tstamp.perf" into ./t (after `cd $t && ...`) 2) -lxperf=4 adds "--repeat 4" to perf stat invocation. 3) -lxperf=(key=val) pairs known key=value pairs (with =defaults given) - tool=perf # path to tool - cmd=stat # todo try others\, perf record\, etc - reps=1 # - rptdir # write reports to a separate data-repo\, safe from git clean -dxf - name # to convey branch-name and/or config-info\, tstamp is prefixed\, - opts # passthru options to perf-stat
$ENV{TEST_OPTS} is split on /;/ and prepended to @ARGV before option handling\, so the following export will affect both make jobs.
export TEST_OPTS="-v;-lxperf=reps=3:rptdir=$HOME/perl/perfdata" make test make test_harness
NOTES:
Test script output under perf stat --repeat 4 violates the "plan just once" rule of TAPv13 spec. It could be extended:
"The plan cannot appear in the middle of the output\, only at beginning or end. Multiple sets of (plan + tests) are allowed\, if all plans agree"
perf stat --repeat N causes perf to compute std-deviation(s) for each measure. 1st example below is w/o repeat\, 2nd with it\, corresponding to the TEST and harness examples above. I dont know how to read into the numbers\, but theres value in having them; they provide some estimate of "noise-floor" on performance for a given test.
The -opts option passthru to perf stat allows "-x\," to cause perf stat to emit CSV output. This is easier to parse than the human readable output\, but doesnt include the computed/normalized values\, nor the name that the "Performance counter stats" (see examples) are for.
TODO
Probable rework of -lxperf option parsing - no way now to get output to STDOUT\, only to file. maybe not worth having - keep (k=v:)+ form - use name="%B-%G-%T.perf" by default "$branch-$sha1st6-$timestamp.perf" - use wr=1 to save file - dir=$HOME/perfruns (shorten rptdir)
Using reps=2 yields "FAILED--seen duplicate leader" on every test.
Fixing this requires changes to TEST's \
The command wrapper template is pretty minimal and constrained; the output file name is "$dir/$timestamp$name.perfstat"\, chosen to match with $timestamp.ttimes so that both file-types are browsable as a pair.
TEST_OPTS is split on ';'\, -lxperf is split on ':' into k=v pairs. There may be scenarios where these delimiters are inconvenient\, or the simplistic parse is brittle.
Performance counter stats for './perl base/cond.t' (3 runs):
t/TEST | 33 ++++++++++++++++++++++++++++++++- 1 file changed\, 32 insertions(+)\, 1 deletion(-)
$options->{utf8}"; $cmd = $perl . _quote_args($args) . " $test $redir"; -- 1.8.3.1
From acfd39ca5d655d2aa4afd5317ef116e5c844373b Mon Sep 17 00:00:00 2001 From: Jim Cromie \jim\.cromie@​gmail\.com Date: Wed\, 20 Nov 2013 11:43:57 -0700 Subject: [PATCH 08/11] t/TEST: simplify \<$results> processing loop. - TAP13.1+
Support use of the --repeat=3 option of linux's perf stat. This basically means extending the TAPv13 spec (or t/TEST's implementation) to allow repeated (ie R) plan executions (ie R occurrences of "1..N" plus the preceding or following N * "ok"s)\, as long as all R plans have the same N.
When a test script is run (under linux perf with --repeat=N)\, the value of R is unavailable in the output; it is transparent other than the repetition itself. But we woundnt want it anyway; TAP readers dont need to handle a new kind of input. If we just allow R repetitions of 1..N tests\, we get loose coupling and dont care if --repeat=5 were given.
Current legal TAP is essentially either:
print "ok $_\n" for 1..N; # 1A print "1..N\n"; # OR [1] print "1..N\n"; # 1B print "ok $_\n" for 1..N;
The big simplification here is that under --repeat\, leading vs trailing "1..N"s are an irrelevant detail.
- "1..N" plans are only allowed before any tests\, or after all of them\, ie ($next==0 or $next==$plan). We just verify this when "1..N" is seen in test output.
- $plan = undef initially\, updated to N when "1..N" is 1st seen.
- $next=0 when "1..N" is seen [2].
- when 2nd+ "1..N" plans are seen\, they are allowed if they agree on N.
- The change to if (defined $plan) accepts "1..0" as legal (ie SKIPs).
- $seen_leader and $trailing_leader are thus obsolete\, replaced where needed by "if ($plan)"\, which is set only when "1..N" is seen.
- $seen_ok was used with $seen_leader to reset $next (test-count). now handled in [2]
- $max is also taken right from "1..N"\, replaced with \<some-expr>($plan)
NOTES:
[1]: this patch allows BOTH 1A then 1B to run successfully\, but not 1B followed by 1A; the latter would fail on N+1 th test\, because the now-trailing "1..N" failed to reset $next. This is an unimportant corner case and doesnt warrant cluttering details in the code. We are running maintained regression tests here\, not logic bombs.
- On "1..N" occurrences: $Reps++ to count repeats (tested at end) reset $next = 0 after validating it [1] $nextreps++\, like $next w/o reset.
- post-loop tests: change ($next == $max) test to ($nextreps == $Reps * $plan)\, which avoids the now resetting $next.
TODO:
This patch supports --repeat N in t/TEST only; harness is strict wrt "only 1 plan"\, ala TAPv13\, so make test_harness complains as follows\, and fails the tests.
comp/use.t ........................................................ All 84 subtests passed comp/retainedlines.t .............................................. All 75 subtests passed comp/cmdopt.t ..................................................... All 44 subtests passed
Sort whats reported in summary data; unique tests or repeated tests ? Reduce $totmax vs $max vs $Reps a bit\, extra/redundant state is not helpful.
t/TEST | 87 +++++++++++++++++++++++++++++++----------------------------------- 1 file changed\, 41 insertions(+)\, 46 deletions(-)
1.8.3.1
From d9f883dd51b0749fcb2a25a1cfad88436c694beb Mon Sep 17 00:00:00 2001 From: Jim Cromie \jim\.cromie@​gmail\.com Date: Thu\, 21 Nov 2013 16:22:09 -0700 Subject: [PATCH 09/11] t/TEST: change timings Storable key: perf -> times\, a better description
Commit 8e03ad8f6c wrote the tests' timing data to a Storable file using 'perf' as the storage key\, but now that we can capture real perf stat data during make test\, the old name is misleading - change it to "times" to better describe its origin and character.
t/TEST | 12 ++++++------ 1 file changed\, 6 insertions(+)\, 6 deletions(-)
1.8.3.1
From 2c86dc105ab67b46e636728d5387226703347e47 Mon Sep 17 00:00:00 2001 From: Jim Cromie \jim\.cromie@​gmail\.com Date: Thu\, 5 Dec 2013 19:29:15 -0700 Subject: [PATCH 10/11] t/TEST: suppress 2 uninitialized envars under make test.valgrind
Recent addition of -w on shebang exposed 2 uninitialized vars\, due to VG_OPTS envar added in commit 11b1a7c9\, which added glue to reuse t/TEST's support for make test.valgrind to run linux perf. The 2 use-cases are:
1. make test.valgrind 2. export VG_OPTS='stat -o perf-stat --append --' export VALGRIND=/usr/bin/perf export VG_TEST=--help make test.valgrind
Since 2 is rather non-obvious\, clarify with comment here and in code.
TODO: this patch is old\, and either needs to be revalidated\, or perhaps rethought; use-case 2 is mostly obsoleted by -lxperf option\, but case 1 still holds.
t/TEST | 4 +++- 1 file changed\, 3 insertions(+)\, 1 deletion(-)
VALGRIND=/usr/bin/perf + # VG_OPTS='stat -o perf-stat --append --' is also needed to run perf this way. my ($sub) = split /\s/\, $ENV{VG_OPTS}; $$toolnm .= "-$sub"; } -- 1.8.3.1
From 4f036d1a02062ca62a5351b2c96f0f151402043d Mon Sep 17 00:00:00 2001 From: Jim Cromie \jim\.cromie@​gmail\.com Date: Thu\, 5 Dec 2013 21:28:50 -0700 Subject: [PATCH 11/11] t/TEST: RFC start to separate out valgrind test support.
This patch creates an empty t/TestValgrind.pm file\, and requires it from t/TEST when ENV{PERL_VALGRIND} is set. As such its seeks to reinterpret the comments at the top of t/TEST.
I propose that the "no require allowed" rule appply to code reached from "make test" without options.
Code used only for special case testing\, like "make test.valgrind"\, or with options passed in via $ENV{TEST_OPTS}\, need not be constrained like this.
A broken require is not something seen until the statement is executed and throws an error. There is nothing special about require at parse-time that must be avoided\, unless we're more than typically paranoid.
make test.valgrind /bin/sh -e ./runtests choose ./perl TEST sh -c valgrind --log-fd=3 --suppressions=perl.supp --leak-check=yes --leak-resolution=high --show-reachable=yes --num-callers=50 --track-origins=yes ./perl -I.. -MTestInit porting/podcheck.t 3>podcheck.t.valgrind-current valgrind --log-fd=3 --suppressions=perl.supp --leak-check=yes --leak-resolution=high --show-reachable=yes --num-callers=50 --track-origins=yes ./perl -I.. -MTestInit porting/podcheck.t
If this argument is accepted\, it looks simple to move the VALGRIND related code blocks into new subroutines in the now-empty TestValgrind.pm file\, and call them appropriately.
MANIFEST | 1 + t/TEST | 4 ++++ t/TestValgrind.pm | 1 + 3 files changed\, 6 insertions(+) create mode 100644 t/TestValgrind.pm
harness b4 requiring us return 1; }
+if ($ENV{PERL_VALGRIND}) { + require TestValgrind; +} + chdir 't' if -f 't/TEST'; if (-f 'TEST' && -f 'harness' && -d '../lib') { @INC = '../lib';
1.8.3.1
[jimc@groucho perl]$
On Mon Nov 03 15:35:51 2014\, yoduh wrote:
From: Jim Cromie \jim\.cromie@​gmail\.com Date: Fri\, 19 Oct 2012 21:29:39 -0600 Subject: [PATCH 02/11] t/TEST: move our @found out to its real scope
Fine\, another solution would be to just remove the our in each case\, since this isn't strict.
From: Jim Cromie \jim\.cromie@​gmail\.com Date: Sat\, 16 Nov 2013 11:32:44 -0700 Subject: [PATCH 06/11] t/TEST: move do_nothing test after option-handling code
I don't think breaking harness is acceptable.
From: Jim Cromie \jim\.cromie@​gmail\.com Date: Wed\, 20 Nov 2013 11:43:57 -0700 Subject: [PATCH 08/11] t/TEST: simplify \<$results> processing loop. - TAP13.1+
This would fail to detect a bug where a test script output its test output twice\, even without --repeat=N
If we're running with --repeat=N we're doing performance testing\, perhaps an option to send the test output to /dev/null instead would be better.
Tony
The RT System itself - Status changed from 'new' to 'open'
I decided to take the leap and apply this set\, on the principle that more perfomance (tooling) is good. Even though I seem to lack the 'perf' tool in any Linux box I can access. If there are problems\, we can hammer them down.
On Thu Nov 06 18:07:30 2014\, jhi wrote:
I decided to take the leap and apply this set\, on the principle that more perfomance (tooling) is good. Even though I seem to lack the 'perf' tool in any Linux box I can access. If there are problems\, we can hammer them down.
As you asked on IRC\, here are some of the problems\, most of which Jim mentions:
- it breaks -v and -torture for harness:
tony@mars:.../perl/t$ ./perl harness -v io/semctl.t
io/semctl.t .. ok
All tests successful.
Files=1\, Tests=2\, 0 wallclock secs ( 0.02 usr 0.00 sys + 0.01 cusr 0.01 csys = 0.04 CPU)
Result: PASS
(where's my raw test output?)
- TEST now accepts duplicate TAP\, which can potentially be caused by a bug:
tony@mars:.../perl/t$ cat badtap.t #!perl print \<\<EOS x 2; 1..2 ok 1 ok 2 EOS tony@mars:.../perl/t$ ./perl badtap.t 1..2 ok 1 ok 2 1..2 ok 1 ok 2 tony@mars:.../perl/t$ ./perl TEST badtap.t t/badtap ... Use of uninitialized value $dir in hash element at TEST line 260. ok All tests successful. u=0.00 s=0.00 cu=0.00 cs=0.00 scripts=2 tests=4
- the patches were submitted as RFC\, some discussion might be useful first.
Tony
On Thu Nov 06 19:27:47 2014\, tonyc wrote:
- the patches were submitted as RFC\, some discussion might be useful first.
Also\, the last patch\, which became 08ac0af6a0260a3939c4904c299200adee71010 doesn't do anything useful\, it's just an "idea" patch above moving valgrind support out of TEST itself.
Tony
On Thursday-201411-06\, 22:27\, Tony Cook via RT wrote:
- the patches were submitted as RFC\, some discussion might be useful first.
Sorry\, pulled the trigger too fast. I now reverted the whole thing.
On Fri\, Nov 07\, 2014 at 06:41:48AM -0500\, Jarkko Hietaniemi wrote:
On Thursday-201411-06\, 22:27\, Tony Cook via RT wrote:
- the patches were submitted as RFC\, some discussion might be useful first.
Sorry\, pulled the trigger too fast. I now reverted the whole thing.
I continue to feel strongly that if such features belong anywhere\, it's in t/harness\, not t/TEST
t/TEST needs to be reliable\, and the best way to achieve that is KISS.
t/harness can do the clever stuff.
If anything\, this also means that we should migrate existing funky stuff from t/TEST to t/harness
Nicholas Clark
Migrated from rt.perl.org#123119 (status was 'open')
Searchable as RT123119$