-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
Skip Doctrine DBAL on php 8 until we have a compatible version #36895
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
Conversation
05ba2a7
to
a6abee6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there anything we can do to help have a tagged version of DBAL compatible with PHP 8 asap?
Can we try adding support for DBAL 3 right now?
There shouldn't be much to do on our side. We might be compatible as soon as the ORM is compatible. |
does this mean we can make |
I'll look into this. |
a6abee6
to
c579db6
Compare
The cache testsuite passes with DBAL 3 on php 8. |
c579db6
to
1090738
Compare
Thank you @derrabus. |
….x on php 8 (derrabus) This PR was merged into the 4.4 branch. Discussion ---------- [Cache][Lock][Messenger] Don't execute tests with DBAL 2.x on php 8 | Q | A | ------------- | --- | Branch? | 4.4 | Bug fix? | yes | New feature? | no | Deprecations? | no | Tickets | #36872 | License | MIT | Doc PR | N/A Follow-up to #36895: If we autoload the `PDOConnection` from DBAL 2.x during a test on php8, our test suite goes 💥 What this PR does: * Some more Cache tests are skipped if DBAL 2 is installed on php 8. * The Lock and Messenger components are tested against DBAL 3. Commits ------- 7dc3f9c Don't execute tests with DBAL 2.x on php 8.
This PR skips all tests on php 8 that would trigger an autoload on DBAL's
PDOConnection
. Those tests would exit with a fatal error because of incompatible method signatures (see doctrine/dbal#3791) and until we can test against a compatible version of DBAL, there's (at least from my point of view) nothing we can do about it. Once this issue is resolved, we can revert this change.