You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run npm run start -- --pathToTheme=/mnt/shared/brite second time I got and error when the script tried to execute docker-compose.
If I remove the docker images the script worked again without any issue.
Here is the output of a script execution without removing the docker images:
iulian@iulian-VirtualBox:~/theme-review-action$ npm run start -- --pathToTheme=/mnt/shared/brite
> wordpress-theme-check-action@1.4.11 start /home/iulian/theme-review-action
> node bin/program.js "--pathToTheme=/mnt/shared/brite"
Test Version: 1.4.11
Testing Ports: 8484/8485
Steps:
✔ Copying theme files into the environment... (in 0s 799ms)
✔ Checking theme's basic structure (in 0s 686ms)
✖ Setting up the development environment for testing...
Error: Command failed with exit code 1: npm run --prefix /home/iulian/theme-review-action/ install:environment
✖ Error while running docker-compose command.
Building wordpress
Service 'wordpress' failed to build: The command '/bin/sh -c pecl install xdebug && docker-php-ext-enable xdebug' returned a non-zero code: 1
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! wordpress-theme-check-action@1.4.11 wp-env: `wp-env "start"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the wordpress-theme-check-action@1.4.11 wp-env script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/iulian/.npm/_logs/2021-08-17T14_59_31_493Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! wordpress-theme-check-action@1.4.11 install:environment: `npm run install:variables && npm run wp-env start && node bin/configure.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the wordpress-theme-check-action@1.4.11 install:environment script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/iulian/.npm/_logs/2021-08-17T14_59_31_522Z-debug.log
> wordpress-theme-check-action@1.4.11 install:environment /home/iulian/theme-review-action
> npm run install:variables && npm run wp-env start && node bin/configure.js
> wordpress-theme-check-action@1.4.11 install:variables /home/iulian/theme-review-action
> node bin/create-wp-env-override.js
Maybe creating .wp-env override config.
No need for an override.
> wordpress-theme-check-action@1.4.11 wp-env /home/iulian/theme-review-action
> wp-env "start"
Step 1/6 : FROM wordpress
---> 8a0af18ec64a
Step 2/6 : RUN apt-get -qy install $PHPIZE_DEPS && touch /usr/local/etc/php/php.ini
---> Running in 512b85044810
Reading package lists...
Building dependency tree...
Reading state information...
autoconf is already the newest version (2.69-11).
dpkg-dev is already the newest version (1.19.7).
file is already the newest version (1:5.35-4+deb10u2).
g++ is already the newest version (4:8.3.0-1).
gcc is already the newest version (4:8.3.0-1).
libc6-dev is already the newest version (2.28-10).
make is already the newest version (4.2.1-1.2).
pkg-config is already the newest version (0.29-6).
re2c is already the newest version (1.1.1-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Removing intermediate container 512b85044810
---> bfb6045f53e1
Step 3/6 : RUN pecl install xdebug && docker-php-ext-enable xdebug
---> Running in d7fa3291686e
pecl/xdebug is already installed and is the same as the released version 3.0.4
install failed
✔ Tearing down the environment... (in 12s 268ms)
Error: Unable to start environment.
We ran into an error with the test framework.
The text was updated successfully, but these errors were encountered:
Hello,
When I run
npm run start -- --pathToTheme=/mnt/shared/brite
second time I got and error when the script tried to executedocker-compose
.If I remove the docker images the script worked again without any issue.
Here is the output of a script execution without removing the docker images:
The text was updated successfully, but these errors were encountered: