Create a script to generate a filled database dump and use it to replace the pseudo-RC1 one we currently have [#2600086]

Follow-up to #2592665: Create RC1 database dumps

In that issue, we added a drupal-8-rc1.filled.standard.php.gz dump, but it was generated by starting with drupal-8.filled.standard.php.gz, which was manually created around beta-12, and then running update.php on it to get it to RC1. This means that if a fresh install of RC1 yields a slightly different database, our automated test coverage isn't testing the update of such a database, even though that's the more common scenario (more people started on RC1 than on beta-12). This will get even more pronounced when we release 8.0.0: it will be more important for us to have automated tests for a fresh 8.0.0 to 8.0.1 update than for an update that starts from a pre-released version of 8.x.

It would also be useful to compare a database that was generated from a fresh install of a given tag/commit-hash with one generated from an earlier tag/commit-hash and then updated. Such comparisons could help uncover bugs with our updates.

So, this issue is to create a script for generating a "filled.standard" database dump, comparing its output with the drupal-8-rc1.filled.standard.php.gz we currently have, and based on that comparison, either replacing that one, or adding it as an additional one.

Comment	File	Size	Author
#7	updatepathrc1testbasefilledtest_log.txt	103.54 KB	Mile23

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

23 October 2015 at 20:27

effulgentsia created an issue. See original summary.

Comment #2

alexpott

he/they

English

🇪🇺🌍

CreditAttribution: alexpott at Chapter Three commented 23 October 2015 at 20:40

Priority:	Critical	» Major
Issue tags:		+d8accelerate grant available

I don't think this is in itself a critical release blocker - however given the possible use cases we decided that this work would be eligible for a d8 accelerate grant.

Comment #3

plach

he/him

Italian

Venezia

CreditAttribution: plach as a volunteer commented 3 November 2015 at 22:50

This means that if a fresh install of RC1 yields a slightly different database, our automated test coverage isn't testing the update of such a database, even though that's the more common scenario (more people started on RC1 than on beta-12).

And this is exactly what's happening in #2607364: RC1 filled database update fails due to beta-12 to RC1 upgrade path issue.

Comment #4

3 November 2015 at 22:50

Version:

8.0.x-dev

» 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Comment #5

3 November 2015 at 22:50

Version:

8.1.x-dev

» 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Comment #6

3 November 2015 at 22:50

Version:

8.2.x-dev

» 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Comment #7

Mile23

English

Seattle, WA

CreditAttribution: Mile23 as a volunteer commented 21 March 2017 at 01:57

File	Size
updatepathrc1testbasefilledtest_log.txt	103.54 KB

Pinging this issue because I see consistent failures with UpdatePathRC1TestBaseFilledTest locally under MAMP, and I got here from #2607364: RC1 filled database update fails due to beta-12 to RC1 upgrade path issue which was a search result for that test name.

Attached is a log of the typical error.

Comment #8

21 March 2017 at 01:57

Version:

8.3.x-dev

» 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Comment #9

21 March 2017 at 01:57

Version:

8.4.x-dev

» 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Comment #10

21 March 2017 at 01:57

Version:

8.5.x-dev

» 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Comment #11

21 March 2017 at 01:57

Version:

8.6.x-dev

» 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Comment #12

21 March 2017 at 01:57

Version:

8.8.x-dev

» 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.