Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
See #2520526: Calculate configuration entity dependencies on install:
- Every new post update has to be added an array - making this test certain fail if you an a post update to core
- Post updates support batches but it is not explicitly tested here.
Release candidate phase evaluation
Issue category | Task because only improving test coverage. |
---|---|
Issue priority | Normal because only making testing easier and improving explicit coverage. |
Unfrozen changes | Unfrozen because it only changes tests. |
Comment | File | Size | Author |
---|---|---|---|
#11 | revert.patch | 4.27 KB | catch |
#3 | 2581459-3.patch | 4.27 KB | alexpott |
Comments
Comment #2
dawehnerFor this particular issue I think it is enough to switch form assert Equal to a checking that at least these 5 update functions are in the state.
Comment #3
alexpottComment #4
dawehnerPerfect!
Comment #5
yched CreditAttribution: yched commentedTHANK YOU
Comment #6
Wim LeersHallelujah! I'd use emojis, but Drupal 7 doesn't support that, so using ASCII instead:
kill it with fire
!Comment #7
effulgentsia CreditAttribution: effulgentsia at Acquia commentedThis only changes a test, so tagging "rc eligible" per https://www.drupal.org/core/d8-allowed-changes#rc.
Comment #9
effulgentsia CreditAttribution: effulgentsia at Acquia commentedPushed to 8.0.x.
Comment #10
catchLooks like this broke PHP 7:
https://www.drupal.org/pift-ci-job/56619
Comment #11
catchSending revert for a test run.
Comment #12
dawehnerThere are certainly tests failing which are unrelated with updates in general, it could be just "random" PHP7 failures.
Comment #13
catchYeah it's not a regression introduced here anyway: https://www.drupal.org/pift-ci-job/57019 Apologies for the false alarm.