Skip to content
Snippets Groups Projects
Commit b7c42ac6 authored by Ben Gamari's avatar Ben Gamari
Browse files

hadrian: Don't capture RunTest output

There are a few reasons why capturing the output of the RunTest builder
is undesirable:

 * there is a large amount of output which then gets unnecessarily
   duplicated by Hadrian if the builder fails

 * the output may contain codepoints which are unrepresentable in the
   current codepage on Windows, causing Hadrian to crash

 * capturing the output causes the testsuite driver to disable
   its colorisation logic, making the output less legible.
parent eb368078
No related branches found
No related tags found
No related merge requests found
...@@ -304,6 +304,11 @@ instance H.Builder Builder where ...@@ -304,6 +304,11 @@ instance H.Builder Builder where
Makeindex -> unit $ cmd' [Cwd output] [path] (buildArgs ++ [input]) Makeindex -> unit $ cmd' [Cwd output] [path] (buildArgs ++ [input])
Tar _ -> cmd' buildOptions echo [path] buildArgs Tar _ -> cmd' buildOptions echo [path] buildArgs
-- RunTest produces a very large amount of (colorised) output;
-- Don't attempt to capture it.
RunTest -> cmd echo [path] buildArgs
_ -> cmd' echo [path] buildArgs _ -> cmd' echo [path] buildArgs
-- TODO: Some builders are required only on certain platforms. For example, -- TODO: Some builders are required only on certain platforms. For example,
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment