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
Trying out PHPUnit 3.5 got me confused for two days. First, I tried to add new tests for some new models I created in Symfony2 PR3's sandbox, which failed with a weird error:
RuntimeException: PHP Parse error: parse error in C:\(...)\symony2_pr3\- on line 131 (notice the \- at the end of the path)
Thinking it was related to Symfony, I left it there. Today, I wanted to introduce PHPUnit into another (non-Symfony) project. Eventually, I ran into the same error:
RuntimeException: PHP Parse error: parse error in C:\(...)\MyProject\- on line 141 (again, notice the \- at the end of the path)
After some trial-and-error, I removed processIsolation="true" from phpunit.xml, and all worked!
I tried debugging the error, but even using xdebug's profiler I wasn't able to locate the origin of the error.
The text was updated successfully, but these errors were encountered:
Could you provide the exact command you are using to execute this test? Also, it would be helpful if you could provide your configuration file and a simple test case that reproduces this error.
I was able to get process isolation working on Windows 7 (x86-64) with PHP 5.3.2 and PHPUnit 3.5.0RC2, so any extra information you can provide would be really helpful.
Trying out PHPUnit 3.5 got me confused for two days. First, I tried to add new tests for some new models I created in Symfony2 PR3's sandbox, which failed with a weird error:
Thinking it was related to Symfony, I left it there. Today, I wanted to introduce PHPUnit into another (non-Symfony) project. Eventually, I ran into the same error:
After some trial-and-error, I removed
processIsolation="true"
from phpunit.xml, and all worked!I tried debugging the error, but even using xdebug's profiler I wasn't able to locate the origin of the error.
The text was updated successfully, but these errors were encountered: