Describe the bug
Occasionally, when running wp-cypress on CircleCI, we see the failure below.
Usually a rerun of the job fixes it
> wp-cypress start
- Checking for Docker
wp-cypress ✔ Docker found
- Creating test container
wp-cypress ✔ Test container created
- Waiting for database connection
wp-cypress ✔ Database connected
- Installing wp-cypress dependencies
wp-cypress ✔ Dependencies installed
- Creating wp-config.php
wp-cypress ✔ wp-config.php created
- Creating database
wp-cypress ✔ Database created
- Installing WordPress
wp-cypress ✔ WordPress installed
- Activating plugins
wp-cypress ✔ Activated plugins
- Set user to admin
wp-cypress ✖ Error: 'wp-cypress-set-user' is not a registered wp command. See 'wp help' for available commands.
To Reproduce
No known way to reproduce
Additional context
I managed to get logs off of CircleCI and they have the error as below
[2021-09-09T15:03:49.402Z] Exited with code 0
[2021-09-09T15:03:52.466Z] stdout: Success: WordPress installed successfully.
[2021-09-09T15:03:52.617Z] Exited with code 0
[2021-09-09T15:03:53.904Z] stderr: Warning: require(/var/www/html/wp-includes/class-wp-theme-json-resolver.php): failed to open stream: No such file or directory in /var/www/html/wp-settings.php on line 174
[2021-09-09T15:03:53.905Z] stderr: Fatal error: require(): Failed opening required '/var/www/html/wp-includes/class-wp-theme-json-resolver.php' (include_path='.:/usr/local/lib/php') in /var/www/html/wp-settings.php on line 174
[2021-09-09T15:03:53.907Z] stderr: Error: There has been a critical error on this website.Learn more about troubleshooting WordPress. There has been a critical error on this website.
[2021-09-09T15:03:54.104Z] Exited with code 255
Describe the bug
Occasionally, when running wp-cypress on CircleCI, we see the failure below.
Usually a rerun of the job fixes it
To Reproduce
No known way to reproduce
Additional context
I managed to get logs off of CircleCI and they have the error as below