Speed System.Web.Mvc.Test back up

[dougbu]

Local builds often look like they're hung for an extended period. When run with /p:BuildInParallel=false or /p:TestInParallel=false, see output similar to the following

  xUnit.net MSBuild Runner (32-bit Desktop .NET 4.0.30319.42000)
    Discovering: System.Web.Mvc.Test
    Discovered:  System.Web.Mvc.Test
    Starting:    System.Web.Mvc.Test
    Finished:    System.Web.Mvc.Test
  === TEST EXECUTION SUMMARY ===
     System.Web.Mvc.Test  Total: 5496, Errors: 0, Failed: 0, Skipped: 0, Time: 3958.681s

Those 66 minutes to execute tests in that assembly are way long. Most assemblies test in less than a minute. Just run other runs for longer than 5 minutes.

Similar long builds are not visible on the CI, tending to build in about 20 minutes. However AppVeyor build duration varies widely from ~25 minutes to ~55 minutes. Builds prior to 5403af6 tended to build in ~8 minutes. That commit added a large number of tests and affected only System.Net.Http.Formatting.Test.

Likely this slowness and variability (not all builds are this slow) relates to system changes and not our code changes. AppVeyor and local dev machines are kept more up-to-date than our CI agents. Then, again, the problem might relate to #95 or system-specific interactions with the recently-upgraded test dependencies (also done last October / November).

[mkArtakMSFT]

@dougbu, so are you certain these are related to the environment changes? How long do the local runs take?

[mkArtakMSFT]

Low priority, let's fix when we'll get a chance.

[dougbu]

so are you certain these are related to the environment changes?

No, only speculating at this point.

How long do the local runs take?

As shown in the original post, just testing the one project can take more than an hour. Local builds taking 45 minutes are common and that greatly reduces productivity in this repo.

[dougbu]

Self-assigning since we want this soon-ish.

[mkArtakMSFT]

Closing as we don't plan to do this given it's a low priority work.