Skip to content

Eliminate the effervescence of windows in FSharpQA tests when using hosted compiler #26

@latkin

Description

@latkin

For those who are actually running all of the tests, current defaults for the FSharpQA suite are to use parallel execution + hosted compiler server. This results is a new compiler server console popping up and dying away every few seconds, which is rather disruptive if you are trying to do other work.

It's a simple change to make those windows hidden, just update constant in runall.pl to CREATE_NO_WINDOW.

Hosted compiler was initially very unreliable, so it was nice to be able to see the output. But it seems sturdy enough now, I think I will change the behavior to something less disruptive.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions