Open garrettmflynn opened 2 weeks ago
To test whether a Linux build works, we will need to enable a large Linux runner at the organization level.
For now, I've stopped Linux builds from being automatically triggered when pushing to latest
latest
The following error is triggered near the end of a Linux CI build.
Packaging with electron-builder • electron-builder version=23.6.0 os=6.5.0-1021-azure • packaging platform=linux arch=x64 electron=26.2.1 appOutDir=.commoners/electron/linux-unpacked • downloading url=https://github.com/electron/electron/releases/download/v26.2.1/electron-v26.2.1-linux-x64.zip size=98 MB parts=8 • downloaded url=https://github.com/electron/electron/releases/download/v26.2.1/electron-v26.2.1-linux-x64.zip duration=1.309s ⨯ write /home/runner/work/vame-desktop/vame-desktop/.commoners/electron/linux-unpacked/electron: no space left on device github.com/develar/app-builder/pkg/fs.WriteFileAndRestoreNormalPermissions /Volumes/data/Documents/app-builder/pkg/fs/file.go:83 github.com/develar/app-builder/pkg/archive/zipx.(*Extractor).extractAndWriteFile /Volumes/data/Documents/app-builder/pkg/archive/zipx/unzip.go:244 github.com/develar/app-builder/pkg/archive/zipx.Unzip.func1.1 /Volumes/data/Documents/app-builder/pkg/archive/zipx/unzip.go:104 github.com/develar/app-builder/pkg/util.MapAsyncConcurrency.func2 /Volumes/data/Documents/app-builder/pkg/util/async.go:68 runtime.goexit /usr/local/Cellar/go/1.17/libexec/src/runtime/asm_amd64.s:1581 ExecError: /home/runner/work/vame-desktop/vame-desktop/node_modules/app-builder-bin/linux/x64/app-builder process failed ERR_ELECTRON_BUILDER_CANNOT_EXECUTE Exit code: 1 at ChildProcess.<anonymous> (/home/runner/work/vame-desktop/vame-desktop/node_modules/builder-util/src/util.ts:250:14) at Object.onceWrapper (node:events:632:26) at ChildProcess.emit (node:events:517:28) at maybeClose (node:internal/child_process:1098:16) at Process.ChildProcess._handle.onexit (node:internal/child_process:303:5) { exitCode: 1, alreadyLogged: false, code: 'ERR_ELECTRON_BUILDER_CANNOT_EXECUTE' }
To test whether a Linux build works, we will need to enable a large Linux runner at the organization level.
For now, I've stopped Linux builds from being automatically triggered when pushing to
latest
The following error is triggered near the end of a Linux CI build.