From: Jesse Luehrs Date: Wed, 27 Jun 2012 18:10:58 +0000 (-0500) Subject: add a few comments to bisect-runner.pl docs X-Git-Tag: upstream/5.20.0~6224 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=f7f0fdee1d58ef2156184ae0b7356ecd6c0c37a0;p=platform%2Fupstream%2Fperl.git add a few comments to bisect-runner.pl docs ./perl -Ilib t/op/sort.t won't do what you want, because tests that don't use Test::More don't set an error code on their own, you need to run it under the harness --- diff --git a/Porting/bisect-runner.pl b/Porting/bisect-runner.pl index ea1534b..e0dd65d 100755 --- a/Porting/bisect-runner.pl +++ b/Porting/bisect-runner.pl @@ -114,6 +114,8 @@ bisect.pl - use git bisect to pinpoint changes .../Porting/bisect.pl --expect-fail --match '\buseithreads\b' # When did this test program stop working? .../Porting/bisect.pl -- ./perl -Ilib ../test_prog.pl + # When did this test start failing? + .../Porting/bisect.pl -- ./perl -Ilib t/TEST op/sort.t # When did this first become valid syntax? .../Porting/bisect.pl --target=miniperl --end=v5.10.0 \ --expect-fail -e 'my $a := 2;' @@ -152,10 +154,12 @@ end revisions. By default F will process all options, then use the rest of the command line as arguments to list C to run a test case. By default, the test case should pass (exit with 0) on earlier perls, and fail (exit -non-zero) on I. F will use F to find the -earliest stable perl version on which the test case passes, check that it -fails on blead, and then use F with C to -find the commit which caused the failure. +non-zero) on I (note that running most of perl's test files directly +won't do this, you'll need to run them through a harness to get the proper +error code). F will use F to find the earliest +stable perl version on which the test case passes, check that it fails on +blead, and then use F with C to find the +commit which caused the failure. Because the test case is the complete argument to C, it is easy to run something other than the F built, if necessary. If you need to run