"Error: write EPIPE" in Travis

Version

3.0.0-rc.11

Node and OS info

Node 8.11.3 / yarn 1.9.4 / Travis Trusty without sudo

Steps to reproduce

In a Travis environment:

• Run yarn build (which runs vue-cli-service build --modern)
• Or run yarn test:unit (which runs vue-cli-service test:unit --runInBand)

What is expected?

It should not throw errors.

What is actually happening?

This is yarn build output:

Starting type checking service...
Using 1 worker with 2048MB memory limit
events.js:183
      throw er; // Unhandled 'error' event
      ^
Error: write EPIPE
    at _errnoException (util.js:992:11)
    at WriteWrap.afterWrite [as oncomplete] (net.js:864:14)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
{ Error: EPIPE: broken pipe, write errno: -32, code: 'EPIPE', syscall: 'write' }
{ Error: EPIPE: broken pipe, write errno: -32, code: 'EPIPE', syscall: 'write' }
{ Error: EPIPE: broken pipe, write errno: -32, code: 'EPIPE', syscall: 'write' }

---

This problem just happens after migrating our code base from PWA template to vue-cli 3.

I don’t know if it’s related to vue-cli-service or yarn or Travis, because I have another command (yarn lint which runs vue-cli-service lint) and it’s working properly.

Also, sometimes it works fine… there is no errors… 🤔

By the way, I don’t have this kind of problem when running those commands:

• on my laptop: Node 9.11.2, yarn 1.7.0, Debian 9.5
• on production server: Node 8.11.3, yarn 1.9.2, Debian 9.5

Thanks you!

[LinusBorg]

Would it help to set parallel to false (= no thread-loader), or is that even slower than threadloader + full vm?

https://cli.vuejs.org/config/#parallel

[jvanst]

Boot-times are about 30s longer, a trade off I’m willing to take for now.