id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc	lang	patch	platform
1412	Remove 'running-make-test'	jkeenan	jkeenan	"In the course of a #parrot discussion today of a test failure reported by darbelo, plobsing and I attempted to figure out what ''t/harness'' option `--running-make-test` does.

I grepped the repository and came up with this:
{{{
./docs/intro.pod:148:
   C:\Perl\bin\perl.exe t\harness --gc-debug --running-make-test
./lib/Parrot/Harness/Options.pm:31:
      $longopts{running_make_test} = grep { $_ eq '--running-make-test' } @argv;
./lib/Parrot/Harness/Options.pm:32:
      @argv = grep { $_ ne '--running-make-test' } @argv;
./lib/Parrot/Harness/Options.pm:133:
      --running-make-test
./t/pharness/03-handle_long_options.t:25:
      --running-make-test
./t/pharness/03-handle_long_options.t:31:
  ok($longopts->{running_make_test}, ""Captured long option"");
./t/harness:34:
  $ENV{RUNNING_MAKE_TEST} = $longopts->{running_make_test};
./t/harness:192:=item C<--running-make-test>
./config/gen/makefiles/root.in:1890:
  # The --running-make-test argument is currently used by long-running tests
./config/gen/makefiles/root.in:1892:
  EXTRA_TEST_ARGS := --gc-debug --running-make-test
}}}

I couldn't see what difference setting `$ENV{RUNNING_MAKE_TEST}` made.  I conducted an Internet search using a well-known search engine, and only came up with links to Parrot posts -- many by me!  (Eeek!)

plobsing++ suggested cutting `running-make-test` (in all its casings and punctuations) out of the distro post-2.0 and seeing what breaks.  To explore that, I have created the ''no_running_make_test'' branch in SVN.

Can anyone shed any light on what `running-make-test` is supposed to be doing?  Is it simply an historical artifact?

Thank you very much.

kid51"	RFC	closed	normal		testing	1.9.0	medium	fixed		plobsing		applied