Skip to content
\n

you can check it here: https://github.com/sonata-project/SonataPageBundle/actions/runs/19821636939/job/56785090042?pr=1832

\n

test: https://github.com/sonata-project/SonataPageBundle/blob/4.x/tests/Functional/Admin/BrowserTest.php

\n

I tried to downgrade to symfony/panther:~2.2.0, but it has the same problem 🤔

\n

Edit: when I downgrade to 2.2.0, those are the packages changed

\n
  - Downgrading symfony/dom-crawler (v8.0.0 => v7.4.0): Extracting archive\n  - Downgrading symfony/panther (v2.3.0 => v2.2.0): Extracting archive\n
\n

and I run the test again, it is the output:

\n
Time: 00:04.237, Memory: 66.50 MB\n\nThere were 3 errors:\n\n1) Sonata\\PageBundle\\Tests\\Functional\\Admin\\BrowserTest::testCrudUrls\nSymfony\\Component\\Panther\\Exception\\RuntimeException: The port 9080 is already in use.\n\n/home/erison/projects/SonataPageBundle/vendor/symfony/panther/src/ProcessManager/WebServerReadinessProbeTrait.php:40\n/home/erison/projects/SonataPageBundle/vendor/symfony/panther/src/ProcessManager/WebServerManager.php:76\n/home/erison/projects/SonataPageBundle/vendor/symfony/panther/src/PantherTestCaseTrait.php:120\n/home/erison/projects/SonataPageBundle/vendor/symfony/panther/src/PantherTestCaseTrait.php:180\n/home/erison/projects/SonataPageBundle/tests/Functional/BasePantherTestCase.php:39\n
\n

and I saw some old issues related with this

\n

symfony/panther#169
\nsymfony/panther#436

\n

But it was working 😄

","upvoteCount":1,"answerCount":1,"acceptedAnswer":{"@type":"Answer","text":"

Please configure display_errors in your CI workflow (for instance by using ini-file: development instead of the default ini-file: production in the setup-php action).
\nThis should give you a better error message when phpunit fails due to a fatal error in the code: sebastianbergmann/phpunit#6382

","upvoteCount":1,"url":"https://github.com/symfony/symfony/discussions/62596#discussioncomment-15125092"}}}
Discussion options

You must be logged in to vote

Please configure display_errors in your CI workflow (for instance by using ini-file: development instead of the default ini-file: production in the setup-php action).
This should give you a better error message when phpunit fails due to a fatal error in the code: sebastianbergmann/phpunit#6382

Replies: 1 comment 2 replies

Comment options

You must be logged in to vote
2 replies
@eerison
Comment options

@eerison
Comment options

Answer selected by eerison
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants