Electron-builder: Travis NSIS EPIPE error

Created on 22 Aug 2017  Â·  41Comments  Â·  Source: electron-userland/electron-builder


  • Version: 19.24.1

  • Target: Windows, Linux | ia32, x64


I have the following .travis.yml, and I get the following error in the Travis log.

dist: trusty
sudo: required

language: node_js
node_js: '8'

env:
  global:
    - ELECTRON_CACHE=$HOME/.cache/electron
    - ELECTRON_BUILDER_CACHE=$HOME/.cache/electron-builder

os:
  - linux

cache:
  directories:
    - node_modules
    - "$HOME/.cache/electron"
    - "$HOME/.cache/electron-builder"
    - "$HOME/.npm/_prebuilds"

addons:
  apt:
    packages:
    - libsecret-1-0

before_install:
  - mkdir -p /tmp/git-lfs && curl -L https://github.com/github/git-lfs/releases/download/v2.2.0/git-lfs-linux-amd64-2.2.0.tar.gz | tar -xz -C /tmp/git-lfs --strip-components 1 && /tmp/git-lfs/git-lfs pull
  - curl -L https://yarnpkg.com/latest.tar.gz | tar xvz && mv dist $HOME/.yarn
  - export PATH="$HOME/.yarn/bin:$PATH"
  - sudo add-apt-repository ppa:ubuntu-wine/ppa -y && sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF && echo "deb http://download.mono-project.com/repo/debian wheezy main" | sudo tee /etc/apt/sources.list.d/mono-xamarin.list && sudo apt-get update && sudo apt-get install --no-install-recommends -y mono-devel ca-certificates-mono wine1.8 gcc-multilib g++-multilib icnsutils graphicsmagick xz-utils

install:
  - yarn

script:
  - yarn dist --linux --win --ia32 --x64

before_cache:
  - rm -rf $HOME/.cache/electron-builder/wine

branches:
  except:
  - "/^v\\d+\\.\\d+\\.\\d+$/"
Building NSIS installer
  Packaging NSIS installer for arch x64
  Packaging NSIS installer for arch ia32
Downloading nsis-3.0.1.13, please wait
Downloading nsis-resources-3.1.0, please wait
Error: write EPIPE
    at _errnoException (util.js:1041:11)
    at WriteWrap.afterWrite (net.js:858:14)
error Command failed with exit code 1.
reply-needed

Most helpful comment

A shitton of people are having this problem. Stop making them stale,

All 41 comments

I am sure that it is temporary problem.

Anyway, I recommend you to remove sudo: required, - sudo add-apt-repository ppa:ubuntu-wine/ppa .... and just use our docker image — https://github.com/electron-userland/electron-builder/wiki/Docker (please be aware https://github.com/electron-userland/electron-builder/issues/1867)

Hmmm... could you provide a .travis.yml using that?

@cawa-93 could you please provide your Travis config?

Does that user docker?
I've edited that .travis.yml because I don't need OSX builds.

I've added the debug env value and here's the new output:

End of NSIS script.
/home/travis/.cache/electron-builder/nsis/nsis-3.0.1.13/linux/makensis: relocation error: /home/travis/.cache/electron-builder/nsis/nsis-3.0.1.13/linux/makensis: symbol _ZNSt7__cxx1112basic_stringIwSt11char_traitsIwESaIwEE10_M_replaceEmmPKwm, version GLIBCXX_3.4.21 not defined in file libstdc++.so.6 with link time reference
Error: /home/travis/.cache/electron-builder/nsis/nsis-3.0.1.13/linux/makensis exited with code 127
    at ChildProcess.childProcess.once.code (/home/travis/build/moriczgergo/musicsort/node_modules/electron-builder-util/src/util.ts:179:14)
    at Object.onceWrapper (events.js:318:30)
    at emitTwo (events.js:125:13)
    at ChildProcess.emit (events.js:213:7)
    at maybeClose (internal/child_process.js:927:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
error Command failed with exit code 255.

I recommend you to build windows on macOS, exactly as in the provided sample travis file. To avoid any issues with Linux Zoo. Is it suitable for you?

I'm having the exact same problem with the newest release of electron-builder on travis. What is the cause?

@nukeop Please try 20.0.2 and file a new issue if need.

Didn't fix it, the 20.0.2 version of the builder still crashes with the same error.

  • downloading               path=/home/travis/.cache/electron-builder/nsis/nsis-resources-3.3.0 url=https://github.com/electron-userland/electron-builder-binaries/releases/download/nsis-resources-3.3.0/nsis-resources-3.3.0.7z
Error: write EPIPE
    at exports._errnoException (util.js:1020:11)
    at WriteWrap.afterWrite (net.js:800:14)

I have the same issue :(

Can this be reopened? I have no problems with building on Windows, but unfortunately travis doesn't offer windows machines.

@nukeop Please try 20.0.4 and set env DEBUG=electron-builder and attach log of the terminal output.

According to release notes nothing related to Windows builds has changed since 20.0.2 where the issue still existed.

Travis output (highlighted relevant line):

https://travis-ci.org/nukeop/nuclear/jobs/341145410#L4999

I can build on Ubuntu but when trying to build windows target on centos7 I get exactly same exception. I suspect it's one of the dependencies but haven't had luck fixing it yet.

I have the same issue with gitlab-ci
Watch this link https://www.npmjs.com/package/epipebomb

This is not relevant anymore for me. Feel free to close it if you want to.

@moriczgergo Why not relevant?

@develar I have deprecated the project that would’ve used it, and Travis support was removed from it long ago.

By the way, I am still encountering this issue, if you need any information on the project to help reproduce this I would be happy to help

I am also encountering this issue on Debian when building for Windows. I am able to build fine on Ubuntu.

Same thing here...
running as cli version 20.20.4 under centos 7 (wine is installed)

I have this error in debian and in centos 7

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Travis now offers Windows machines so maybe this will be obsolete.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Not doing anything is never a good reason to close tickets in my humble opinion. So I don't know what good this bot is supposed to be doing.

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

Not doing anything is never a good reason to close tickets in my humble opinion. So I don't know what good this bot is supposed to be doing.

Closed for the third time for inactivity...

For what it's worth, electron-builder works fine in Github Actions when building on Windows machines.

For what it's worth, electron-builder works fine in Github Actions when building on Windows machines.

Cool. Do you have an example we could have a look at? Thanks.

Yes.

Example recent run: https://github.com/nukeop/nuclear/runs/282512732
And the simple action that launched it: https://github.com/nukeop/nuclear/blob/master/.github/workflows/build.yml

I've also been experimenting with automated deployment on a separate branch, which mostly works, I just don't know how to upload several artifacts to a single release yet.
https://github.com/nukeop/nuclear/blob/feature/actions-deployment/.github/workflows/build.yml

@globaltommy @albertotorresfoltyn I am also getting the same error on Centos 7 and on Ubuntu it's working fine. If you have applied any solution to it, Can you help me in that?

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

A shitton of people are having this problem. Stop making them stale,

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

this is just comedic now

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

Actually. This issue is not relevant for me now. Is it work as expected now?

Because if so I can close the issue

Was this page helpful?
0 / 5 - 0 ratings