Update: drupal/core:9.5.11

Created on 7 December 2023, 12 months ago
Updated 8 December 2023, 12 months ago

Problem/Motivation

https://git.drupalcode.org/project/acquia_migrate/-/tree/2023-09-27 is pinned to https://www.drupal.org/project/drupal/releases/9.5.8 β†’

Steps to reproduce

N/A

Proposed resolution

  1. MR against the recommendations branch to update recommendations.json to use https://www.drupal.org/project/drupal/releases/9.5.11 β†’
  2. Verify the recommendations tests pass in GitLab CI
  3. MR against the 1.8.x (module) branch to pin the module to this new branch
  4. Verify the module tests pass in GitLab CI
  5. Tag new recommendations release
  6. Update the MR against 1.8.x to pin to the new tag
  7. If any non-.gitlab-ci.yml changes were necessary in the MR against 1.8.x, then tag a new module release to

Remaining tasks

User interface changes

None.

API changes

None.

Data model changes

None.

πŸ“Œ Task
Status

Fixed

Version

1.8

Component

Recommendations

Created by

πŸ‡§πŸ‡ͺBelgium wim leers Ghent πŸ‡§πŸ‡ͺπŸ‡ͺπŸ‡Ί

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @wim leers
  • πŸ‡§πŸ‡ͺBelgium wim leers Ghent πŸ‡§πŸ‡ͺπŸ‡ͺπŸ‡Ί

    I followed the official handbook page for this process β†’

    1. Step 1: no issues.
    2. Step 2:
      1. Applying https://www.drupal.org/files/issues/2022-12-20/3204212-field-migration-widget-formatter-mapping-52--fix-only.patch …
        patching file core/modules/datetime/src/Plugin/migrate/field/DateField.php
        patching file core/modules/field/migrations/d6_field_formatter_settings.yml
        patching file core/modules/field/migrations/d6_field_instance_widget_settings.yml
        Hunk #2 FAILED at 45.
        1 out of 2 hunks FAILED -- saving rejects to file core/modules/field/migrations/d6_field_instance_widget_settings.yml.rej
        patching file core/modules/field/migrations/d7_field_instance_widget_settings.yml
        patching file core/modules/field/src/Plugin/migrate/field/Email.php
        patching file core/modules/field/src/Plugin/migrate/field/d7/EntityReference.php
        patching file core/modules/file/src/Plugin/migrate/field/d6/FileField.php
        patching file core/modules/file/src/Plugin/migrate/field/d7/FileField.php
        patching file core/modules/image/image.module
        patching file core/modules/image/src/Plugin/migrate/field/d6/FileField.php
        patching file core/modules/migrate_drupal/src/Plugin/migrate/field/FieldPluginBase.php
        patching file core/modules/migrate_drupal/src/Plugin/migrate/field/d6/NodeReference.php
        patching file core/modules/migrate_drupal/src/Plugin/migrate/field/d6/NumberDecimalField.php
        patching file core/modules/migrate_drupal/src/Plugin/migrate/field/d6/NumberFloatField.php
        patching file core/modules/migrate_drupal/src/Plugin/migrate/field/d6/NumberIntegerField.php
        patching file core/modules/migrate_drupal/src/Plugin/migrate/field/d6/UserReference.php
        patching file core/modules/migrate_drupal/src/Plugin/migrate/field/d7/Boolean.php
        patching file core/modules/taxonomy/src/Plugin/migrate/field/TaxonomyTermReference.php
        patching file core/modules/telephone/src/Plugin/migrate/field/d6/PhoneField.php
        patching file core/modules/telephone/src/Plugin/migrate/field/d7/PhoneField.php
        patching file core/modules/text/src/Plugin/migrate/field/d6/TextField.php
        

        πŸ‘† Thankfully @slasher13 already provided a reroll: #3204212-57: Convert remaining widget and formatter type migrations to MigrateField plugins β†’ . Credited him.

      2. Updated the patch to point to the new one, and tried again. Next failure:
        Applying https://www.drupal.org/files/issues/2020-04-08/2985882-field-85.patch …
        patching file core/modules/layout_builder/src/Plugin/Derivative/FieldBlockDeriver.php
        Reversed (or previously applied) patch detected!  Assume -R? [n] 
        

        πŸ‘† Looks like πŸ’¬ Workaround for "Call to a member function getLabel() after enabling layout_builder" Fixed actually was committed after 9.5.8?! πŸ˜„ Yes, it was: #2985882-164: Workaround for "Call to a member function getLabel() after enabling layout_builder" β†’ . And shipped in 9.5.9: https://www.drupal.org/project/drupal/releases/9.5.9 β†’ β€” yay one fewer core patch to maintain!

      3. Removed that patch, tried again … and success! πŸ₯³
  • Merge request !13Update drupal/core to 9.5.11 β†’ (Merged) created by wim leers
  • πŸ‡§πŸ‡ͺBelgium wim leers Ghent πŸ‡§πŸ‡ͺπŸ‡ͺπŸ‡Ί

    Looks like there's some GitLab CI infrastructure instability… requeued the 2 failed test jobs that failed with similar errors (while other identical tests against different PHP versions worked just fine).

  • πŸ‡§πŸ‡ͺBelgium wim leers Ghent πŸ‡§πŸ‡ͺπŸ‡ͺπŸ‡Ί

    #6 was solved in πŸ› GitLab CI pipeline broke due to wodby/php:8.1-dev 4.41.0 installing XDebug 3.3 Needs review . Rebasing this and then retrying…

  • πŸ‡§πŸ‡ͺBelgium wim leers Ghent πŸ‡§πŸ‡ͺπŸ‡ͺπŸ‡Ί

    So this part is done now:

    1. MR against the recommendations branch to update recommendations.json to use https://www.drupal.org/project/drupal/releases/9.5.11 β†’
    2. Verify the recommendations tests pass in GitLab CI

    Next up:

    <ol start=3>
      <li>MR against the <code>1.8.x

    (module) branch to pin the module to this new branch

  • Verify the module tests pass in GitLab CI
  • πŸ‡§πŸ‡ͺBelgium wim leers Ghent πŸ‡§πŸ‡ͺπŸ‡ͺπŸ‡Ί

    Wim Leers β†’ changed the visibility of the branch mr-origin-16 to hidden.

  • Status changed to RTBC 12 months ago
  • πŸ‡§πŸ‡ͺBelgium wim leers Ghent πŸ‡§πŸ‡ͺπŸ‡ͺπŸ‡Ί

    Results show RefreshDetectionTest is failing even on the "next recommendations", even though those are still the same as the scheduled pipeline tests, which passed earlier today.

    I have noticed that particular test failing quite regularly, but intermittently. A re-test usually fixes it.

    Conclusion: all tests are passing as expected.

  • πŸ‡§πŸ‡ͺBelgium wim leers Ghent πŸ‡§πŸ‡ͺπŸ‡ͺπŸ‡Ί

    Done:

    1. MR against the 1.8.x (module) branch to pin the module to this new branch
    2. Verify the module tests pass in GitLab CI

    Which only leaves:

    1. Tag new recommendations release
    2. Update the MR against 1.8.x to pin to the new tag
    3. If any non-.gitlab-ci.yml changes were necessary in the MR against 1.8.x, then tag a new module release to

    … but that is out of scope for this issue. I'll create a separate issue for that to ensure there is at least one occurrence of this happening that is explicitly documented, so that others could do this in the future πŸ‘

    • Wim Leers β†’ committed 473f22f5 on recommendations
      Issue #3406774 by Wim Leers, slasher13: Update: drupal/core:9.5.11
      
  • Status changed to Fixed 12 months ago
  • πŸ‡§πŸ‡ͺBelgium wim leers Ghent πŸ‡§πŸ‡ͺπŸ‡ͺπŸ‡Ί
  • πŸ‡§πŸ‡ͺBelgium wim leers Ghent πŸ‡§πŸ‡ͺπŸ‡ͺπŸ‡Ί

    Created πŸ“Œ .gitlab-ci.yml: ensure module MR to test a recommendations MR is possible Needs review to ensure nobody else has to fight that CI infra again.

  • Issue was unassigned.
  • πŸ‡§πŸ‡ͺBelgium wim leers Ghent πŸ‡§πŸ‡ͺπŸ‡ͺπŸ‡Ί
  • πŸ‡§πŸ‡ͺBelgium wim leers Ghent πŸ‡§πŸ‡ͺπŸ‡ͺπŸ‡Ί
  • Automatically closed - issue fixed for 2 weeks with no activity.

  • Production build 0.71.5 2024