magento / magento/magento-cloud-docker
PHPUnit doesn't work with magento/magento-cloud-docker-php:8.3-fpm-1.3.7 image
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 277
- Forks
- 187
- PR merge metrics
- No merged PRs in 30d
Description
I'm not able to run PHPUnit when using the `magento/magento-cloud-docker-php:8.3-fpm-1.3.7` image
It works fine with `magento/magento-cloud-docker-php:8.2-fpm-1.3.7` and `magento/magento-cloud-docker-php:8.2-fpm-1.3.6`
### Preconditions
Generate a Magento Cloud Docker docker-compose.yml file using this command:
`./vendor/bin/ece-docker 'build:compose' --host='dev.local' --mode=developer --with-xdebug --os='2.12' --db='10.6' --php='8.3' --rmq='3.12' --redis='7.2'`
1. Run docker-compose up -d
### Steps to reproduce
1. Run `docker exec -it magento2_fpm_xdebug_1 bash`
2. Run `php -d xdebug.mode=coverage vendor/bin/phpunit --version`
### Expected result
PHPUnit version returned, for example:
`PHPUnit 9.6.19 by Sebastian Bergmann and contributors.`
### Actual result
Segmentation fault (core dumped)

Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by generating the docker-compose.yml with the listed ece-docker build:compose command, then enter the magento2_fpm_xdebug_1 container and run the reported PHP coverage command. Compare the 8.3-fpm-1.3.7 image with the working 8.2 images to isolate the cause. Done means PHPUnit reports its version without a segmentation fault on the affected image.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, php
- Domain
- devops, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100