-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PHPUnit 6.0 does not work with PHP 7.0.0-7.0.12 #2470
Comments
I can reproduce this with PHP 7.0.7 on Windows 10:
|
I cannot reproduce this with PHP 7.1.1 on Windows 10:
Looks like this is related to the PHP version rather than to the operating system. |
That's just pure luck on the non-deterministic order that files get required I think? |
The PHAR does not use autoloading. |
I can reproduce this with PHP 7.0.7 on Linux. |
Okay, it looks like this is a similar issue to the one fixed in 1044b8e. It will be fixed shortly. It's interesting, though, that recent/current versions of PHP 7 do not seem to be affected by this. At least they do not error out on startup. |
👍 |
As you can see in https://travis-ci.org/sebastianbergmann/phpunit/builds/198346201, the current state of the |
@nikic just explained: "As of 7.0.13 collisions are only checked within a single file, always. Previously that depended on symbol type, file order and whether or not you're using opcache. Basically it's fine to shadow a symbol in the namespace using an import, as long as it's not blatantly wrong (shadowing a symbol in the same file)." |
Relevant bug on the PHP side: https://bugs.php.net/bug.php?id=66773 |
PHPUnit does not work since I updated it to 6.0 from 5.7.9.
The error message is as below:
On PHPUnit 6.0.3
On PHPUnit 6.0.0, 6.0.1, and 6.0.2 (Maybe this message is the same as #2460 )
I'm using PHPUnit with XAMPP on Windows 7 SP1 (64bit), and XAMPP is installed in
D:\xampp
.I met the error in the following steps:
phpunit-6.0.3.phar
is downloaded automatically.phpunit
.D:\xampp\php
.> phpunit --version
on cmd.exeThe text was updated successfully, but these errors were encountered: