Testing issue for mysql56

Part of the review cleanup. Not closing out as you seem to be using. Can run the tests by clicking add test/retest though.

Thanks. Sorry for leaving it NR. Postponed is actually the more accurate status until I need to run tests again. And thank you for all your work on cleaning up the Needs Review queue!

The last submitted patch, 83: test-mysql56-D101-83.patch, failed testing. View results →

One failure required updating mysql56_requirements() to merge in core's updates to mysql_requirements().

For TimestampFormatterSettingsUpdateTest, I don't even know how that's passing in HEAD (but it is) without refreshing the local $config_factory, but this should fix it at least within this patch.

Another reroll for upstream composer.lock drift.

With #86 being green, I released https://www.drupal.org/project/mysql56/releases/8.x-1.6-beta1 → .

Back to marking this issue as postponed until test runs are needed again.

Rerolled for a test run ahead of 10.1's release.

Fixed upstream typo

#91 is green so I released https://www.drupal.org/project/mysql56/releases/8.x-1.6 → . Back to postponed here until another test run is needed.

It's that time of year :)

Surprised the bot didn't pick this up. But Seems to have test failures.

Question from the issue summary this is a workaround for drupalCi but what about gitlab?

I set #95 to NR just to queue tests, but now back to NW to keep this out of the review queue.

Question from the issue summary this is a workaround for drupalCi but what about gitlab?

It's a good question as to whether with GitLabCI if it's now possible to move this issue to the https://www.drupal.org/project/mysql56 → queue but still be able to put some custom stuff into that project's .gitlab-ci configuration that would make it run all of Drupal core's tests. I'll need to look into that when I can carve out some time to do so.