Run 2.x branch at D10 and not D11

Uploading patch to allow testing at D9, which has to have protected $strictConfigSchema = FALSE. See 🐛 Label token replacement for views entity reference arguments not working Needs work

Things are getting better - here is the latest pipeline:
https://git.drupalcode.org/project/scheduler_content_moderation_integrat...

The D10 phpunit job now only fails on one test, HookUpdateTest::testUpdates with the deprecation error

Exception: Deprecated function: mb_strtolower(): Passing null to parameter
    #1 ($string) of type string is deprecated
    Drupal\Core\Config\Entity\Query\Condition->compile()() (Line: 39)

This was dealt with in 3.x by simply deleting that test

At D9 just one test LayoutBuilderTest::testLayoutBuilder fails, with

Behat\Mink\Exception\ExpectationException: Current response status code is 500, but 200 expected

Locally this passes, so I can't replicate it to investigate.

After some investigation I found that the LayoutBuilder internal server error 500 on D9 is somewhat random. The job has passed, then on a re-run of the same pipeline it fails. So I have skipped the end of that test just for D9.

The HookUpdateTest fails due to stricter conditions on null in D10, probably due to the contents of the database dumps. Therefore this test can be skipped at D10, still runs OK on D9.

Fixed.

I'm using this issue fork to test general pipeline changes. They do not need separate MRs, we can test in a branch, then pick the commits. I have created a 3.x test branch

This issue can be left 'fixed' and then will become 'closed (fixed)' but I can continue to use the issue forks.

jonathan1055 → changed the visibility of the branch 3502119-D10-for-2.x-branch to hidden.

The 8.x-1.x pipeline now passes and is fully green.

jonathan1055 → changed the visibility of the branch 3.0.x to hidden.

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