Downgrade PHP for the DB2 workflow #7134
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
TIL: I cannot pin the PHP patch release with the Setup PHP action. 😓 |
derrabus
force-pushed
the
chore/db2-segfault
branch
from
ac96714 to
d3166ca
Compare
derrabus
force-pushed
the
chore/db2-segfault
branch
from
d3166ca to
dfcbe83
Compare
greg0ire
approved these changes
Sep 4, 2025
| - "7.4" | ||
| - "8.4" | ||
| - "8.3" | ||
| # The DB2 workflow currently segfaults with PHP 8.4 |
There was a problem hiding this comment.
It would be great to have a bug report to link to here
There was a problem hiding this comment.
Indeed. If only someone were motivated enough to write a proper bug report. 😬
There was a problem hiding this comment.
Linking a bug report for reference: shivammathur/setup-php#992.
FWIW, I successfully ran the test suite on PHP 8.4.12 with ibm_db2 2.2.2 yesterday on a local Linux machine.
derrabus
added a commit
to derrabus/dbal
that referenced
this pull request
Sep 4, 2025
* 3.10.x: Document the PDO subclasses backport (doctrine#7137) Downgrade PHP for the DB2 workflow (doctrine#7134) Workaround for MySQL 8.4 and unknown users (doctrine#7136) Leverage PHP 8.4 PDO classes, fix PHP 8.5 deprecation (doctrine#7132) Run tests on MySQL 8.4 LTS and 9.4 (doctrine#7133)
derrabus
added a commit
to derrabus/dbal
that referenced
this pull request
Sep 4, 2025
* 4.3.x: Remove obsolete upgrade note (doctrine#7138) Document the PDO subclasses backport (doctrine#7137) Downgrade PHP for the DB2 workflow (doctrine#7134) Workaround for MySQL 8.4 and unknown users (doctrine#7136) Leverage PHP 8.4 PDO classes, fix PHP 8.5 deprecation (doctrine#7132) Run tests on MySQL 8.4 LTS and 9.4 (doctrine#7133)
derrabus
added a commit
to derrabus/dbal
that referenced
this pull request
Sep 4, 2025
* 4.4.x: Remove obsolete upgrade note (doctrine#7138) Document the PDO subclasses backport (doctrine#7137) Downgrade PHP for the DB2 workflow (doctrine#7134) Workaround for MySQL 8.4 and unknown users (doctrine#7136) Leverage PHP 8.4 PDO classes, fix PHP 8.5 deprecation (doctrine#7132) Run tests on MySQL 8.4 LTS and 9.4 (doctrine#7133)
derrabus
added a commit
to derrabus/dbal
that referenced
this pull request
Sep 4, 2025
* 4.4.x: Make options check strict again Make options check strict again (doctrine#7141) Remove obsolete upgrade note (doctrine#7138) Document the PDO subclasses backport (doctrine#7137) Downgrade PHP for the DB2 workflow (doctrine#7134) Workaround for MySQL 8.4 and unknown users (doctrine#7136) Leverage PHP 8.4 PDO classes, fix PHP 8.5 deprecation (doctrine#7132) Run tests on MySQL 8.4 LTS and 9.4 (doctrine#7133)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have no idea why the DB2 workflow started to segfault. My best guess is that there's an incompatibility with the latest patch release of PHP. Let's see if pinning to an older release works.
Update: I've downgraded from PHP 8.4 to 8.3. That seems to "fix" it for now and give us a green CI again. Let's monitor the issue and revert the patch when the issues is solved.