Add core testing with Mysql 8.4 LTS and 9.0

Last commit should be removed as production images will be rolled

Second MR probably preferable

Not sure I follow which MR should be reviewed?

Both but second has less changes

So in MR 8652 this seems to be consistently failing https://git.drupalcode.org/issue/drupal-3458878/-/pipelines/215144

Looks like DB container failed https://git.drupalcode.org/issue/drupal-3458878/-/jobs/2361081

MaxWhitehead → closed merge request !9106

Meantime I published MySQL 9.0.1 image https://dev.mysql.com/doc/relnotes/mysql/9.0/en/

Rebased and added 9.0

Looks related issue solved problem with random failures so I think it ready for review

Next releases of PHP will support new Vector data-type for Mysql 9.0 ref https://github.com/php/php-src/issues/15432

PS: will be released in 8.3.11/8.2.23/8.4.0beta4+

Added link to https://dev.mysql.com/doc/refman/9.0/en/vector.html

Seems to be passing so don't see an issue to add.

Committed/pushed to 11.x, thanks!

Not sure how much we'd want to backport this to 10.4 but moving to 'to be ported' for discussion. MR doesn't apply cleanly so would need a real backport.

andypost → closed merge request !8652

andypost → closed merge request !8653

Backported, thank you!

nit: I'm using 8.3-ubuntu for new jobs, guess no reason to use 8.1

10.4 pipeline looks green.

Looking at tests log which is full of warnings (as they enabled here for debugging purposes)

[service:drupalci/mysql-8-database] 2024-08-29T13:00:47.302353023Z 2024-08-29T13:00:47.302203Z 0 [Warning] [MY-013865] [InnoDB] Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.
[service:drupalci/mysql-8-database] 2024-08-29T13:00:48.783864493Z 2024-08-29T13:00:48.783716Z 0 [Warning] [MY-013865] [InnoDB] Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.
[service:drupalci/mysql-8-database] 2024-08-29T13:00:51.099659581Z 2024-08-29T13:00:51.099573Z 0 [Warning] [MY-013865] [InnoDB] Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.

...
[service:drupalci/mysql-8.4-database] 2024-08-29T13:02:19.154554084Z 2024-08-29T13:02:19.154369Z 0 [Warning] [MY-013865] [InnoDB] Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.
[service:drupalci/mysql-8.4-database] 2024-08-29T13:02:19.936404754Z 2024-08-29T13:02:19.936218Z 0 [Warning] [MY-013865] [InnoDB] Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.
[service:drupalci/mysql-8.4-database] 2024-08-29T13:02:23.006410242Z 2024-08-29T13:02:23.006223Z 0 [Warning] [MY-013865] [InnoDB] Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.
[service:drupalci/mysql-8.4-database] 2024-08-29T13:02:23.595133871Z 2024-08-29T13:02:23.594927Z 0 [Warning] [MY-013865] [InnoDB] Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.

...
Drupal\FunctionalTests\Entity\RevisionRevertFormTest           5 passes                                      
[service:drupalci/mysql-9-database] 2024-08-29T13:05:06.662786573Z 2024-08-29T13:05:06.662624Z 0 [Warning] [MY-013865] [InnoDB] Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.
[service:drupalci/mysql-9-database] 2024-08-29T13:05:08.670726447Z 2024-08-29T13:05:08.670592Z 0 [Warning] [MY-013865] [InnoDB] Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.
Drupal\FunctionalTests\Update\UpdatePathTestBaseTest           6 passes  

Probably we need to tune images a bit

I think this is worth backporting just to ensure that 10.x stays compatible, as we still have a couple of years of support and people might run on newer MySQL while remaining on an older Drupal install.

Committed 7c3cdb7 and pushed to 10.4.x. Thanks!

andypost → closed merge request !9375

Automatically closed - issue fixed for 2 weeks with no activity.