How run electron-builder without fail and build no stop

how to run electron-builder without fail and build not stop
electron-builder is work but failed and exited with 1 during .
how to set travis file ?

same here

language: node_js
    - os: windows
  fast_finish: true
    - name: "build on windows"
      os: windows
    - name: "build on mac"
      os: osx
sudo: false
- '10'
cache: yarn
  - if [ "$TRAVIS_OS_NAME" == "windows" ]; then powershell -command 'Set-MpPreference -DisableRealtimeMonitoring $true'; fi
  - cd ./packages/PROJECTNAME
  - yarn install
  - yarn build:frontend
  - if [ "$TRAVIS_OS_NAME" == "windows" ]; then powershell -command 'yarn package:win'; fi
  - if [ "$TRAVIS_OS_NAME" == "osx" ]; then yarn package; fi

MacOS build runs quick and finishes successfully.
Windows runs without errors, but times out.

module.exports = {
  appId: 'com.electron.${name}',
  directories: {
    output: 'package'
  files: [
  win: {
    target: 'dir'
  mac: {
    target: 'dir'

the commands:

electron-builder --config electron-builder.js --mac
electron-builder --config electron-builder.js --win

Build output before failing:

Child main:
    Hash: 094aa54945b8f6758c95
    Time: 61075ms
    Built at: 06/17/2019 12:21:03 PM
      Asset      Size  Chunks             Chunk Names
    main.js  5.76 KiB       0  [emitted]  main
    Entrypoint main = main.js
     [0] external "electron-better-ipc" 42 bytes {0} [built]
     [1] external "electron-log" 42 bytes {0} [built]
     [2] external "electron" 42 bytes {0} [built]
     [3] external "electron-is-dev" 42 bytes {0} [built]
     [4] ./src/launcher/main/ipc.ts 1.22 KiB {0} [built]
     [5] external "path" 42 bytes {0} [built]
     [6] external "assert" 42 bytes {0} [built]
     [7] ./src/launcher/config.ts 614 bytes {0} [built]
     [8] external "electron-store" 42 bytes {0} [built]
     [9] ./src/launcher/init-log.ts 360 bytes {0} [built]
    [10] external "@sentry/electron" 42 bytes {0} [built]
    [11] ./src/launcher/init-sentry.ts + 1 modules 885 bytes {0} [built]
         | ./src/launcher/init-sentry.ts 162 bytes [built]
         | ./src/launcher/build-vars.ts 718 bytes [built]
    [12] ./src/launcher/main.ts 6.4 KiB {0} [built]
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on:
The build has been terminated

I am building win on a windows machine, because i am using sharp node module as native dependency.

My initial guess is that you have a background process running (e.g., Build doesn't finish after completing tests) that is preventing the shutdown.

i am trying this already :D:

sadly no luck. same problem as before.

I have a before_deploy and deploy step.
So the electron-build command timed out without an error, because the other steps are not called.

GPG may not be the only thing running in the background. The text “Child main” in the logs suggests that the build itself is spawning multiple processes. Please consult the documentation.

i am trying to increase the timeout for that command:

- if [ "$TRAVIS_OS_NAME" == "windows" ]; then travis_wait 30 yarn package:win; fi

no luck. i do not know what is happening … or if there is even anything running.

Any further ideas?

If you can add extra commands , try to get a list of all running processes, to find which needs to be killed.

My guess is electron is running a process to help cache the next build.

when is the best moment to call it?
before the build task it does not make sense and everthing after is not called.

When i use travis_wait the command fails and the process is killed as well.

Maybe run it under wtrace to see what processes are being created and deleted (not sure there is an easy way to correlate the create and kills, so this might be laborious if electron uses lots of processes - try to configure it to go slow and use only one process)

My fault:

my build command (previously only on unix machines) concatenates to commands like this:

&& this caused the described behaviour. So i splitted them up, and now it runs.

Noob mistake :smile: