Problem/Motivation

According to #3222756: Allow using images from external source and #3272969: Remove unique constraint on block content info field our 9.4.4 database dump is wrong.

i.e. it contains configuration which can only match this 10.x-only issue #3257274: Implement color changing theme settings for Olivero.

Assuming these are actually 9.4.4 database dumps, the only way I can think of this happening is if the YAML file cache (which is PHP files) had some items from a 10.x install and they were read when dumping the database?

Last time we did an actual upgrade was in #3290810: Remove updates added prior to 9.4.0 (9.4.4 for ckeditor) and add 9.4.0 database dumps but it could have been introduced when we recreated the dumps in a removal issue.

Steps to reproduce

Proposed resolution

Load the 9.3.0 database dump, checkout Drupal 9.4.4, upgrade the database. Dump the database again and create a patch for 9.5.x

Then, still in 9.4.4 with the upgraded database, uninstall modules that are removed from 10.0.x (quickedit etc.), then dump the database again, and then create a patch for 10.1.x/10.0.x

Verify that the dumps don't re-introduce the same issue again, but applying one of the patches from the above two issues on top of the patch with the database dump in it and ensuring tests still pass.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Comments

catch created an issue. See original summary.

catch’s picture

Category: Task » Bug report
wim leers’s picture

spokje’s picture

Assigned: Unassigned » spokje
wim leers’s picture

👏 @Spokje 🙏

spokje’s picture

StatusFileSize
new1.09 MB
spokje’s picture

StatusFileSize
new1.32 MB

Turns out we need to replace both the bare and the filled fixture.

spokje’s picture

StatusFileSize
new1.43 MB

The-Patch-That-Discovered-It-All (#3222756-85: Allow using images from external source, the 9.5 one) on top of the above new fixtures to (hopefully) show these dumps work.

spokje’s picture

Assigned: spokje » Unassigned

New fixtures (bare and filled) for 10.0.x are still needed according to @catch. I'm signing off for today, if nobody beats me to it, I'll have a look then.

catch’s picture

Just found #3306938: Restore olivero_post_update_add_olivero_primary_color() too (was wondering why the test for that issue wasn't failing, and it's because we removed the test).

spokje’s picture

StatusFileSize
new1.32 MB

Right, seems that these new fixtures didn't held up committing #3222756: Allow using images from external source...

Let's try that test with the new fixtures.

spokje’s picture

StatusFileSize
new1.33 MB

Also let's try 3272969-15.patch with the new 9.4.0 fixtures

spokje’s picture

StatusFileSize
new1.26 MB
spokje’s picture

Somehow the new 9.5 fixtures seems to fail only on PHP 7.3 with a Erroneous data format for unserializing 'Symfony\Component\Routing\Route'

spokje’s picture

catch’s picture

spokje’s picture

Both @catch and @quietone pointed out #3275093: Drupal 9.3.0 dumps were created with PHP 8, needs to be PHP 7.3 which seems to be the answer to the question in #14.

spokje’s picture

StatusFileSize
new1.32 MB
spokje’s picture

StatusFileSize
new1.32 MB
spokje’s picture

StatusFileSize
new1.33 MB
wim leers’s picture

Indeed, #3222756: Allow using images from external source was unblocked because we worked around this bug — see #3222756-89: Allow using images from external source for details. It's a harmless work-around; we didn't want to keep waiting even longer, especially because today the CKEditor 5 upstream release happens that will allow us to solve the last stable blockers! 🤓🥳

spokje’s picture

Ok, the shortcut of importing and exporting the newly created fixtures using PHP7.3 didn't work.

Need to actually _recreate_ them in PHP 7.3.

spokje’s picture

StatusFileSize
new1.33 MB

How about these then for 9.5.x

spokje’s picture

Let's have some proof

spokje’s picture

The test failure on PHP7.3 & SQLite 3.28 seemed like a random one to me. Ordered a retest anyway.

Besides that: I think we might have hit on actual PHP 7.3-proof 9.4.0-fixtures for 9.5.x

spokje’s picture

Looking at the success rate of the automated tests for PHP 7.3 & SQLite 3.28 here: https://www.drupal.org/pift-ci-job/2464611, it looks like we have about 40% chance the test will return green.

I'm not going to use more test-cycles to hit that 40%, seeing the other PHP 7.3 & [insert_your_fav_DB_flavour_here] having passed, I hereby declare the 9.5.x 9.4.0-fixtures as good as I"m going to get them.

spokje’s picture

StatusFileSize
new1.07 MB
spokje’s picture

Status: Active » Needs review

Both the test failures on pgsql and sqlite seem random to me.
Ordered a retest, but I'm pretty sure this can be NR until we await the return of the Get-A-Full-Testrun-Green-On-Anything-Else-But-MySQL.

spokje’s picture

Looking at the Automated testing of PHP 8.1 & sqlite-3.27 here: https://www.drupal.org/pift-ci-job/2465337, there's a 50/50 change of green. Not something I personally want to throw more test-cycles at.

catch’s picture

10.0.x dumps are validated in #3306938: Restore olivero_post_update_add_olivero_primary_color(), so I think we are probably ready to go here.

smustgrave’s picture

Status: Needs review » Reviewed & tested by the community

@catch shared with me the sqlite failure ticket in https://www.drupal.org/project/drupal/issues/1120020. Since this seems to pass mysql and mariaDb fine with marking this RTBC to keep it moving.

alexpott’s picture

Status: Reviewed & tested by the community » Fixed

Committed and pushed d2bd120973 to 10.1.x and 01151f9313 to 10.0.x. Thanks!
Committed ebaa992 and pushed to 9.5.x. Thanks!

  • alexpott committed d2bd120 on 10.1.x
    Issue #3306897 by Spokje, catch: Fix the 9.4.4 database dumps
    

  • alexpott committed 01151f9 on 10.0.x
    Issue #3306897 by Spokje, catch: Fix the 9.4.4 database dumps
    
    (cherry...

  • alexpott committed ebaa992 on 9.5.x
    Issue #3306897 by Spokje, catch: Fix the 9.4.4 database dumps
    
wim leers’s picture

Wow, you made this happen in record time, @Spokje! 👏

Status: Fixed » Closed (fixed)

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