Let's see how much config is changing on install.

This issue is not exploring a bug - it probably is okay to change config during an install - this issue is just finding how often this is occurring and why.

Files: 
CommentFileSizeAuthor
#1 2405709.1.patch1.56 KBalexpott
FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] 83,774 pass(es), 810 fail(s), and 0 exception(s). View

Comments

alexpott’s picture

Status: Active » Needs review
FileSize
1.56 KB
FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] 83,774 pass(es), 810 fail(s), and 0 exception(s). View

Status: Needs review » Needs work

The last submitted patch, 1: 2405709.1.patch, failed testing.

Berdir’s picture

Context?

Can we be sure that this is a bad thing?

We are missing a syncing check, but I think use cases like http://cgit.drupalcode.org/simplenews/tree/simplenews.install?h=8.x-1.x#... are valid? There is no other way to do this.

alexpott’s picture

Issue summary: View changes
jhodgdon’s picture

See also #2394425: Standard profile config/install needs re-export, which I think found mostly the same things from the Config Revert module.

In that issue I actually looked at the list of config that had changed and analyzed why... the Config Revert module omits UUID and dependency components and alphabetizes so it may be more permissive than this test... this test skips UUID but might complain about dependencies?

alexpott’s picture

Afaik dependencies shouldn't change during install

alexpott’s picture

addendum to #6 - dependencies can change during an install - but they really shouldn't

jhodgdon’s picture

Well, when I had dependencies in the module, I got a lot more reports of "this has changed", and they didn't seem relevant because it seems like the config system is fixing them when the config is imported. So, either we shouldn't be considering dependencies, or we need to export a lot more config.

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.

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.

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.