<div dir="ltr"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail_default" style="font-family:tahoma,sans-serif">
There are tests that depend upon haddock in the testsuite, so we need to<br>
build them to run those tests. Like Cheng says, passing `--docs=none`<br>
will avoid those tests.

</div></blockquote><div><br></div><div style="font-family:tahoma,sans-serif" class="gmail_default">But looking at `ps` I see an invocation of haddock that was running for 20 minutes!  This can't be right.</div><div style="font-family:tahoma,sans-serif" class="gmail_default"><br></div><div style="font-family:tahoma,sans-serif" class="gmail_default">Adding --docs=none apparently didn't work.  I get zillions of failures.</div><div style="font-family:tahoma,sans-serif" class="gmail_default"><br></div><div style="font-family:tahoma,sans-serif" class="gmail_default">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</div><div style="font-family:tahoma,sans-serif;margin-left:40px" class="gmail_default">hadrian/build test --docs=none --only=T13199</div><div style="font-family:tahoma,sans-serif" class="gmail_default">But this does not (log below)</div><div style="font-family:tahoma,sans-serif;margin-left:40px" class="gmail_default">hadrian/build test --docs=none --only=T13199 -VV</div><div style="font-family:tahoma,sans-serif" class="gmail_default"><br></div><div style="font-family:tahoma,sans-serif" class="gmail_default">I thought -VV controlled verbosity only!</div><div style="font-family:tahoma,sans-serif" class="gmail_default"><br></div><div style="font-family:tahoma,sans-serif" class="gmail_default">Simon</div><div style="font-family:tahoma,sans-serif" class="gmail_default"><br></div><div style="font-family:tahoma,sans-serif" class="gmail_default">=====> T13199(normal) 1 of 1 [0, 0, 0]<br>cd "/tmp/ghctest-6yc58m02/test   spaces/testsuite/tests/printer/T13199.run" && $MAKE --no-print-directory T13199   < <br> ]0;T13199(normal) 1 of 1 [0, 0, 0] Actual stdout output differs from expected:<br>diff -uw "/dev/null" "/tmp/ghctest-6yc58m02/test   spaces/testsuite/tests/printer/T13199.run/T13199.run.stdout.normalised"< <br>--- /dev/null        2022-07-28 08:52:58.419999998 +0100<br>+++ "/tmp/ghctest-6yc58m02/test   spaces/testsuite/tests/printer/T13199.run/T13199.run.stdout.normalised"       2022-07-28 16:04:06.479419465 +0100<br>@@ -0,0 +1,2 @@<br>+/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<br>+/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<br>*** unexpected failure for T13199(normal)<br><br>Performance Metrics (test environment: local):<br><br><br>None collected.<br><br><br>Unexpected results from:<br>TEST="T13199"<br><br>SUMMARY for test run started at Thu Jul 28 16:04:05 2022 <br>0:00:00.845518 spent to go through<br>       1 total tests, which gave rise to<br>       7 test cases, of which<br>       6 were skipped<br>       0 had missing libraries<br><br>       0 expected passes<br>       0 expected failures<br><br>       0 caused framework failures<br>       0 caused framework warnings<br>       0 unexpected passes<br>       1 unexpected failures<br>       0 unexpected stat failures<br>       0 fragile tests<br><br>Unexpected failures:<br>   /tmp/ghctest-6yc58m02/test   spaces/testsuite/tests/printer/T13199.run  T13199 [bad stdout] (normal)<br></div><div style="font-family:tahoma,sans-serif" class="gmail_default"></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 28 Jul 2022 at 15:23, Zubin Duggal <<a href="mailto:zubin@well-typed.com">zubin@well-typed.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">There are tests that depend upon haddock in the testsuite, so we need to<br>
build them to run those tests. Like Cheng says, passing `--docs=none`<br>
will avoid those tests.<br>
<br>
On 22/07/28 14:47, Simon Peyton Jones wrote:<br>
>Doing *hadrian/build test*<br>
>takes absolutely ages.   It seems that it is building haddock, running<br>
>haddock, building check_exact, and other things.  Eg right now it is doing<br>
>Run Haddock BuildPackage: libraries/parsec/src/Text/Parsec.hs (and 24 more)<br>
>=> _build/doc/html/libraries/parsec-3.1.15.0/parsec.haddock<br>
><br>
>But I didn't ask to do Haddock. I just wanted to run the testsuite.   How<br>
>can I do that?<br>
><br>
>I would prefer never to build haddock.<br>
><br>
>Thanks<br>
><br>
>Simon<br>
<br>
>_______________________________________________<br>
>ghc-devs mailing list<br>
><a href="mailto:ghc-devs@haskell.org" target="_blank">ghc-devs@haskell.org</a><br>
><a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs" rel="noreferrer" target="_blank">http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs</a><br>
<br>
</blockquote></div>