electron-builder: Travis NSIS EPIPE error
- 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.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 45 (7 by maintainers)
A shitton of people are having this problem. Stop making them stale,
Same thing here… running as cli version 20.20.4 under centos 7 (wine is installed)
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.
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
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.
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