Skip to content

bug: builds broken with an uncaught composer error #190

@rhoerr

Description

@rhoerr

I currently get an error on mageos-release:

$ node src/make/mageos-release.js --mageosRelease=1.0.5-p5 --upstreamRelease=2.4.7-p3 --skipHistory
...
5/7 Packaging [1.0.5-p5] Magento_nl_NL
6/7 Packaging [1.0.5-p5] Magento_pt_BR
7/7 Packaging [1.0.5-p5] Magento_zh_Hans_CN
Packaging Magento Base Package
Determining dependencies...
Removing existing temporary workdir at /tmp/workdir-f9f29ed3731da9dea37dc7fc7dab22fc
Preparing temporary copy in /tmp/workdir-f9f29ed3731da9dea37dc7fc7dab22fc
Running composer install --no-progress --no-plugins --no-scripts
Inspecting 6125 files to determine composer dependencies...
node:events:497
      throw er; // Unhandled 'error' event
      ^

Error: spawn php-classes.phar ENOENT
    at ChildProcess._handle.onexit (node:internal/child_process:286:19)
    at onErrorNT (node:internal/child_process:484:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Emitted 'error' event on ChildProcess instance at:
    at ChildProcess._handle.onexit (node:internal/child_process:292:12)
    at onErrorNT (node:internal/child_process:484:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'spawn php-classes.phar',
  path: 'php-classes.phar',
  spawnargs: []
}

Node.js v20.15.1

I've tried various things including updating composer, reinstalling node packages, and updating node packages, but to no avail.

This error appears to affect the upstream mirror builds too, for as long as the action history shows: https://github.com/mage-os/generate-mirror-repo-js/actions/runs/12732736267/job/35488270194#step:8:331

Packaging Magento Base Package
Determining dependencies...
Preparing temporary copy in /tmp/workdir-9867b9034c64e5b7b0c14209e777ea80
Running composer install --no-progress --no-plugins --no-scripts
Inspecting 6180 files to determine composer dependencies...
node:events:496
      throw er; // Unhandled 'error' event
      ^

Error: write EPIPE
    at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:95:16)
Emitted 'error' event on Socket instance at:
    at emitErrorNT (node:internal/streams/destroy:169:8)
    at emitErrorCloseNT (node:internal/streams/destroy:128:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -32,
  code: 'EPIPE',
  syscall: 'write'
}

Node.js v20.18.1
Error: Process completed with exit code 1.

Which makes me wonder if the entire build process is currently broken.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions