CI Builds to support libsysconfcpus

If you take a look at this thread, https://github.com/elm-lang/elm-compiler/issues/1473#issuecomment-245704142 you’ll find that elm make won’t work in almost all CI servers.

And hence running a webpack, will 100% timeout.

[eeue56]

@maraisr No, you should only have 1 elm entry point if you are making a small SPA. If you are making all of your frontend code in Elm, then you have multiple entry points. This is how NoRedInk does it, and this is the repo I am talking about 😉

[rtfeldman]

@klazuka oh, and it actually has access to all 32 cores? If so, I would open an issue on https://github.com/elm-lang/elm-make/issues because that would be an issue with elm-make. (Otherwise, it seems like this is probably an issue with Azure VM mis-reporting like Travis and Circle’s VMs are.)

Regardless, I don’t think this repo is the right place to focus on a fix, so I’m going to close this.

Next steps:

• If you’re on a VM that makes more than 2 cores available (as opposed to reporting more than 2 but only making 2 available, like Travis and Circle do), and things, file an issue at https://github.com/elm-lang/elm-make/issues
• If you’d like to help improve things with a third-party language extension for Travis and Circle, ping rtfeldman on Elm Slack.

Thanks all!