Include slow tests in some configuration

[MikeHolman]

We are adding a bunch of new configurations with #18 and #42. With this, I'm wondering if we can include slow tests in some configuration? Right now seems like we are arbitrarily excluding a number of tests.

[ianwjhalliday]

We currently get slow test coverage from our internal nightlies runs which should cover ChakraCore commits as well, at least once per day. The goal last I heard was to get nightlies moved to rolling and get about three runs of it per day.

Are there particular tests you're concerned about? If we had the resources I'd love to have all the slow tests revisited and either remove them, commit them to nightlies, or reduce their runtime down and bring them back to dev test runs. If there are particular tests you would like to see brought out of slow you could take a look at paring them down to run in a reasonable time (< 5 seconds ideally).

cc @boingoing

[dilijev]

I think the point is that if we're running some configurations once a day in the open, we might as well run the nightlies in the open as well. I tend to agree. The reason we removed them originally was because they were unnecessarily increasing the length of the checks run on each PR which slows down our cadence. Nothing blocks on the daily builds, so it seems reasonable to add them there.

[ianwjhalliday]

Certainly easy to turn them on by just including -includeSlow. I'm fine with turning it on and seeing how it goes.

[dilijev]

@curtisman and @digitalinfinity were part of this discussion last time.

Do you guys think we should turn on -includeSlow in a set of daily build tasks now that we have some? This would be a reason to have a daily build corresponding to each of our regular VS 2015 builds.

[dilijev]

I made a quick change to add some daily configs which use -includeSlow. See #49.

[dilijev]

Closed by #84