The following daily build failed: https://travis-ci.com/guardrdistro/guardr-project/jobs/255944581#L512

Related error:

PHP Fatal error:  Allowed memory size of 1610612736 bytes exhausted (tried to allocate 67108864 bytes) in phar:///home/travis/.phpenv/versions/7.1.11/bin/composer/src/Composer/DependencyResolver/Solver.php on line 223
Fatal error: Allowed memory size of 1610612736 bytes exhausted (tried to allocate 67108864 bytes) in phar:///home/travis/.phpenv/versions/7.1.11/bin/composer/src/Composer/DependencyResolver/Solver.php on line 223

Comments

shrop created an issue. See original summary.

shrop’s picture

shrop commented

Re-ran the job https://travis-ci.com/guardrdistro/guardr-project/jobs/255944586

Still failed. Noting that I see composer self updates to 1.9.1. Not sure if that is related. Might not be.

joestewart’s picture

joestewart commented

prepending "COMPOSER_MEMORY_LIMIT=-1" to the composer install may allow the command to proceed.

Reference: https://getcomposer.org/doc/articles/troubleshooting.md#memory-limit-errors

shrop’s picture

shrop commented

I hit a memory error on local builds using composer create project using the following:

create-project guardrdistro/guardr-project:8.x-dev guardr-project --no-interaction

This did allow it to work: COMPOSER_MEMORY_LIMIT=-1 composer create-project guardrdistro/guardr-project:8.x-dev guardr-project --no-interaction. Don't think this is directly related to this issue, but just to show Joe's comment #3 solution does work.

shrop’s picture

shrop commented
Issue tags: +ContributionWeekend2020
shrop’s picture

shrop commented

Setup this PR: https://github.com/guardrdistro/guardr-project/pull/22 to add COMPOSER_MEMORY_LIMIT=-1 to the composer install command.

The test ran without memory error.

shrop’s picture

shrop commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.