1. 20 Apr, 2011 1 commit
    • Simon Peyton Jones's avatar
      Add TEST_HC_OPTS to every Makefile invocation of TEST_HC · 6c32ee85
      Simon Peyton Jones authored
      In the testsuite there are numerous Makefiles that invoke $(TEST_HC).
      But, unlike the tests invoked directly by the harness, they didn't pass
      -dno-debug-output, or $(EXTRA_HC_OPTS).
      This patch goes part-way towards the goal of making the two consistent:
      * Almost all invocations in the Makefiles now go
          '$(TEST_HC)' $(TEST_HC_OPTS)
      * In test.mk we initialise
           TEST_HC_OPTS = -dno-debug-output $(EXTRA_HC_OPTS)
      Still to come (I don't know how to do these)
      * The invocations of TEST_HC via cabal are not treated
        (eg cabal01, cabal04), and they should be
      * TEST_HC_OPTS should probably be initialised the same way
        as the Python script computes the flags to pass to the
        TEST_HC that it calls directly
  2. 05 May, 2010 1 commit
  3. 04 Sep, 2007 1 commit
  4. 17 Apr, 2007 2 commits
  5. 13 Apr, 2007 1 commit
  6. 11 Mar, 2007 1 commit
  7. 06 Mar, 2007 1 commit
  8. 22 Aug, 2001 1 commit
    • simonmar's avatar
      [project @ 2001-08-22 10:42:32 by simonmar] · 6011b4e5
      simonmar authored
      Use makefiles in the subdirectories to ease running the test driver in
      a subdirectory.  It can be run in the following ways:
       	make		-- run all the tests in the current directory
       	make verbose	-- as make test, but up the verbosity
       	make accept	-- run the tests, accepting the current output
      and you can also set some variables on the command line, eg.
      	make accept TESTS=arr001  -- accept an individual test
      	make EXTRA_HC_OPTS='-v'   -- extra flags to the haskell compiler
      	make CONFIG=<config>	  -- use a different test config
      this will all go in the docs at some point.