Vue-cli parallelism error at building when CPU limitations

[JFGHT]

Version

3.0.0

Node and OS info

Yarn 1.9.4 / CircleCI docker img: circleci/node:10.8-stretch-browsers

Steps to reproduce

• Use the free version of CircleCI.
• Build with CircleCI.

What is expected?

Normal build

What is actually happening?

events.js:183
throw er; // Unhandled 'error' event
^
Error: This socket has been ended by the other party
at Socket.writeAfterFIN (...)

---

Deactivating the parallelism is a workaround. More info here: https://forum.vuejs.org/t/solution-to-building-error-in-circleci-or-any-other-machine-with-cpu-limitations/40862

I think this should be in the docs.

[yyx990803]

Not sure if that's the real cause as our own tests run on free Circle CI.

[JFGHT]

Are you able to reproduce it?

[haoqunjiang]

As quoted here:

The issue with this on Dockerized services such as CircleCI is that the container thinks it has access to all of the hosts cores, although its being limited down to 4 by another process.

I've encountered this issue before, with jest.

[yyx990803]

@JFGHT Vue CLI's own tests runs on Circle CI free tier all the time, and it is passing right now. The only thing I can think of is that we are open source so we get 4 containers by default. Are you building from a private repo? In addition, can you share your Circle CI config.yaml?

One obvious option is disabling parallel by default in CI environments, although I'd like to avoid that if possible, as that would lead to non-optimal performance in CI systems that do support multiple cores.

[JFGHT]

Yes, I'm building in a private repo.

Here is the config.yaml: https://pastebin.com/tJUuktPa

[JFGHT]

Fixed #3850.