Closed Kocal closed 6 years ago
Hum, it will be difficult to give you a depo that reproduce this issue, because this problem happens on a private repo (from work). 😕 Anyway I will try to do something.
For now I will dump some important files, maybe it will help you:
~Oh by the way, I forgot to say that this problem just happens after migrating our code base from PWA template to vue-cli 3. 🤔~ EDIT: added in original post
Interesting, I don't know if it coincidence or not, but I stopped to build the app with --modern
flag and I have no errors anymore. :thinking:
I'm closing for now.
Interesting, now yarn lint
gives me this output:
Starting type checking service...
Using 1 worker with 2048MB memory limit
events.js:183
throw er; // Unhandled 'error' event
^
Error: This socket has been ended by the other party
at Socket.writeAfterFIN [as write] (net.js:364:12)
at PoolWorker.writeJson (/home/travis/build/Yproximite/XXX/node_modules/thread-loader/dist/WorkerPool.js:89:22)
at PoolWorker.run (/home/travis/build/Yproximite/XXX/node_modules/thread-loader/dist/WorkerPool.js:69:12)
at WorkerPool.distributeJob (/home/travis/build/Yproximite/XXX/node_modules/thread-loader/dist/WorkerPool.js:326:20)
at /home/travis/build/Yproximite/XXX/node_modules/thread-loader/node_modules/async/queue.js:10:5
at Object.process (/home/travis/build/Yproximite/XXX/node_modules/thread-loader/node_modules/async/internal/queue.js:175:17)
at /home/travis/build/Yproximite/XXX/node_modules/thread-loader/node_modules/async/internal/queue.js:82:19
at Immediate._onImmediate (/home/travis/build/Yproximite/XXX/node_modules/thread-loader/node_modules/async/internal/setImmediate.js:27:16)
at runCallback (timers.js:810:20)
at tryOnImmediate (timers.js:768:5)
at processImmediate [as _immediateCallback] (timers.js:745:5)
error Command failed with exit code 1.
I will take a look to thread-loader.
I am running into the same problem right now building with TravisCI.
This project is for work but I will make one which I can share the source code of.
3.0.1
OS: Ubuntu 14.04.5 LTS Node: v8.12.0 NPM: 6.4.1 NVM: 0.33.11
Scaffold project with PWA support.
npm run build
(Which runs vue-cli-service build
)
I expect vue-cli to build the appropriate bundles.
Error is being thrown.
> tournkey-client@0.1.0 build /home/travis/build/sport-travel/tournkey-client
> vue-cli-service build
events.js:183
throw er; // Unhandled 'error' event
^
Error: This socket has been ended by the other party
at Socket.writeAfterFIN [as write] (net.js:376:12)
at PoolWorker.writeJson (/home/travis/build/sport-travel/tournkey-client/node_modules/thread-loader/dist/WorkerPool.js:89:22)
at PoolWorker.run (/home/travis/build/sport-travel/tournkey-client/node_modules/thread-loader/dist/WorkerPool.js:69:12)
at WorkerPool.distributeJob (/home/travis/build/sport-travel/tournkey-client/node_modules/thread-loader/dist/WorkerPool.js:326:20)
at /home/travis/build/sport-travel/tournkey-client/node_modules/async/queue.js:10:5
at Object.process (/home/travis/build/sport-travel/tournkey-client/node_modules/async/internal/queue.js:164:17)
at /home/travis/build/sport-travel/tournkey-client/node_modules/async/internal/queue.js:104:15
at /home/travis/build/sport-travel/tournkey-client/node_modules/async/internal/onlyOnce.js:12:16
at callback (/home/travis/build/sport-travel/tournkey-client/node_modules/thread-loader/dist/WorkerPool.js:163:21)
at /home/travis/build/sport-travel/tournkey-client/node_modules/thread-loader/dist/WorkerPool.js:190:15
at /home/travis/build/sport-travel/tournkey-client/node_modules/async/internal/map.js:32:9
at /home/travis/build/sport-travel/tournkey-client/node_modules/async/internal/once.js:12:16
at replenish (/home/travis/build/sport-travel/tournkey-client/node_modules/async/internal/eachOfLimit.js:59:25)
at iterateeCallback (/home/travis/build/sport-travel/tournkey-client/node_modules/async/internal/eachOfLimit.js:49:17)
at /home/travis/build/sport-travel/tournkey-client/node_modules/async/internal/onlyOnce.js:12:16
at /home/travis/build/sport-travel/tournkey-client/node_modules/async/internal/map.js:29:13
at Socket.onChunk (/home/travis/build/sport-travel/tournkey-client/node_modules/thread-loader/dist/readBuffer.js:32:9)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at Socket.Readable.read (_stream_readable.js:475:10)
at flow (_stream_readable.js:846:34)
at resume_ (_stream_readable.js:828:3)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! tournkey-client@0.1.0 build: `vue-cli-service build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the tournkey-client@0.1.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/travis/.npm/_logs/2018-09-13T17_45_55_960Z-debug.log
The command "npm run build" exited with 1.
Done. Your build exited with 1.
{ 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' }
{ 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' }
{ 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' }
{ 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' }
{ 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' }
{ 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' }
{ Error: EPIPE: broken pipe, write errno: -32, code: 'EPIPE', syscall: 'write' }
{ Error: EPIPE: broken pipe, write errno: -32, code: 'EPIPE', syscall: 'write' }
@Kocal Do you have any updates since you last commented?
Well, I simply stopped building modern app in Travis, and I have no errors anymore :man_shrugging:
Update to this.
I was able to solve this by changing the travis build environment from a container based to full virtualization. The thread-loader package does not play nicely with containers that don't use all the threads available.
Read more here: https://docs.travis-ci.com/user/reference/overview/#virtualization-environments
To run in a full virtual machine add sudo: required
to the top of your .travis.yaml
How much boot-time do you lose when using a full VM?
Boot-times are about 30s longer, a trade off I'm willing to take for now.
Would it help to set parallel
to false
(= no thread-loader), or is that even slower than threadloader + full vm?
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:
yarn build
(which runsvue-cli-service build --modern
)yarn test:unit
(which runsvue-cli-service test:unit --runInBand
)What is expected?
It should not throw errors.
What is actually happening?
This is
yarn build
output: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
oryarn
or Travis, because I have another command (yarn lint
which runsvue-cli-service lint
) and it's working properly.Also, sometimes it works fine... there is no errors... :thinking:
By the way, I don't have this kind of problem when running those commands:
Thanks you!