There are tests that depend upon haddock in the testsuite, so we need to
build them to run those tests. Like Cheng says, passing `--docs=none`
will avoid those tests.

But looking at `ps` I see an invocation of haddock that was running for 20 minutes!  This can't be right.

Adding --docs=none apparently didn't work.  I get zillions of failures.

But then it turned out that this failed because I also added -VV, in the hope of seeing what is going on.  So this works
hadrian/build test --docs=none --only=T13199
But this does not (log below)
hadrian/build test --docs=none --only=T13199 -VV

I thought -VV controlled verbosity only!

Simon

=====> T13199(normal) 1 of 1 [0, 0, 0]
cd "/tmp/ghctest-6yc58m02/test   spaces/testsuite/tests/printer/T13199.run" && $MAKE --no-print-directory T13199   <
]0;T13199(normal) 1 of 1 [0, 0, 0] Actual stdout output differs from expected:
diff -uw "/dev/null" "/tmp/ghctest-6yc58m02/test   spaces/testsuite/tests/printer/T13199.run/T13199.run.stdout.normalised"<
--- /dev/null 2022-07-28 08:52:58.419999998 +0100
+++ "/tmp/ghctest-6yc58m02/test   spaces/testsuite/tests/printer/T13199.run/T13199.run.stdout.normalised" 2022-07-28 16:04:06.479419465 +0100
@@ -0,0 +1,2 @@
+/home/simonpj/code/HEAD-1/_build/test/bin/check-ppr   "`'/home/simonpj/code/HEAD-1/_build/stage1/bin/ghc' -dcore-lint -dstg-lint -dcmm-lint -fno-dump-with-ways -no-user-package-db -rtsopts  -fno-warn-missed-specialisations -fshow-warning-groups -fdiagnostics-color=never -fno-diagnostics-show-caret -Werror=compat -dno-debug-output --print-libdir | tr -d '\r'`" T13199.hs
+/home/simonpj/code/HEAD-1/_build/test/bin/check-exact "`'/home/simonpj/code/HEAD-1/_build/stage1/bin/ghc' -dcore-lint -dstg-lint -dcmm-lint -fno-dump-with-ways -no-user-package-db -rtsopts  -fno-warn-missed-specialisations -fshow-warning-groups -fdiagnostics-color=never -fno-diagnostics-show-caret -Werror=compat -dno-debug-output --print-libdir | tr -d '\r'`" T13199.hs
*** unexpected failure for T13199(normal)

Performance Metrics (test environment: local):


None collected.


Unexpected results from:
TEST="T13199"

SUMMARY for test run started at Thu Jul 28 16:04:05 2022
0:00:00.845518 spent to go through
       1 total tests, which gave rise to
       7 test cases, of which
       6 were skipped
       0 had missing libraries

       0 expected passes
       0 expected failures

       0 caused framework failures
       0 caused framework warnings
       0 unexpected passes
       1 unexpected failures
       0 unexpected stat failures
       0 fragile tests

Unexpected failures:
   /tmp/ghctest-6yc58m02/test   spaces/testsuite/tests/printer/T13199.run  T13199 [bad stdout] (normal)

On Thu, 28 Jul 2022 at 15:23, Zubin Duggal <zubin@well-typed.com> wrote:
There are tests that depend upon haddock in the testsuite, so we need to
build them to run those tests. Like Cheng says, passing `--docs=none`
will avoid those tests.

On 22/07/28 14:47, Simon Peyton Jones wrote:
>Doing *hadrian/build test*
>takes absolutely ages.   It seems that it is building haddock, running
>haddock, building check_exact, and other things.  Eg right now it is doing
>Run Haddock BuildPackage: libraries/parsec/src/Text/Parsec.hs (and 24 more)
>=> _build/doc/html/libraries/parsec-3.1.15.0/parsec.haddock
>
>But I didn't ask to do Haddock. I just wanted to run the testsuite.   How
>can I do that?
>
>I would prefer never to build haddock.
>
>Thanks
>
>Simon

>_______________________________________________
>ghc-devs mailing list
>ghc-devs@haskell.org
>http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs