[10.5.x] test DB transaction isolation set to read-committed breaks tests

HEAD is broken due to 🐛 Set default transaction isolation level to READ-COMMITTED in MySQL/MariaDB Active

I think this is the issue to resolve it.

Yes it needs to fix

    Installer Isolation Level Existing Settings (Drupal\Tests\mysql\Functional\InstallerIsolationLevelExistingSettings)
     ✘ Installer
       ┐
       ├ Failed asserting that two strings are equal.
       ┊ ---·Expected
       ┊ +++·Actual
       ┊ @@ @@
       ┊ -'REPEATABLE-READ'
       ┊ +'READ-COMMITTED'
       │
       │ /builds/issue/drupal-3539366/core/modules/mysql/tests/src/Functional/InstallerIsolationLevelExistingSettingsTest.php:58
       ┴

better title for https://git.drupalcode.org/project/drupal/-/blob/11.x/core/modules/mysql...

Replaced comparison with session vs global isolation level

dimitriskr → changed the visibility of the branch 3539366-11.x-tx-isolation-mysql to hidden.

dimitriskr → changed the visibility of the branch 3539366-10.5.x-tx-isolation-mysql to hidden.

I think it's fine for me to RTBC !13038 as not an author

Moreover it needs backport to 10.x

This is affecting MRs now https://git.drupalcode.org/issue/drupal-3015152/-/jobs/6259156

mondrake → changed the visibility of the branch 3539366-fix-tx-isolation to hidden.

Committed/pushed to 11.x and cherry-picked to 11.2,x, thanks!

This doesn't apply against 10.6.x, do we need a backport?

catch → closed merge request !13038

MR 13052 Port to 10.6.x. It also applies clean to 10.5.x.

I bet it require backport

The Needs Review Queue Bot → tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".

This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.

Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.

I think the bot is confused. Updated metadata.

I also reviewed and it like the same as the original fix.

Committed/pushed to 10.6.x and cherry-picked to 10.5.x, thanks!

catch → closed merge request !13052

andypost → closed merge request !13039

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