- Issue created by @wim leers
- π§πͺBelgium wim leers Ghent π§πͺπͺπΊ
I followed the official handbook page for this process β
- Step 1: no issues.
- Step 2:
-
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.
- 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!
- Removed that patch, tried again β¦ and success! π₯³
-
- π§πͺ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:
- MR against the
recommendations
branch to updaterecommendations.json
to use https://www.drupal.org/project/drupal/releases/9.5.11 β - 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
- MR against the
- π§πͺBelgium wim leers Ghent π§πͺπͺπΊ
Wim Leers β changed the visibility of the branch mr-origin-16 to hidden.
- Status changed to RTBC
about 1 year ago 2:43pm 8 December 2023 - π§πͺ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:
- MR against the
1.8.x
(module) branch to pin the module to this new branch - Verify the module tests pass in GitLab CI
Which only leaves:
- Tag new recommendations release
- Update the MR against
1.8.x
to pin to the new tag - If any non-
.gitlab-ci.yml
changes were necessary in the MR against1.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 π
- MR against the
-
Wim Leers β
committed 473f22f5 on recommendations
Issue #3406774 by Wim Leers, slasher13: Update: drupal/core:9.5.11
-
Wim Leers β
committed 473f22f5 on recommendations
- Status changed to Fixed
about 1 year ago 2:48pm 8 December 2023 - π§πͺ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.
Automatically closed - issue fixed for 2 weeks with no activity.