I'm getting failures in the past few days for ConfigUpdateTest, presumably due to a recent Drupal Core commit.

The failures can be seen at
https://www.drupal.org/pift-ci-job/110678
and other recent test runs.

My suspicion is that due to a recent Drupal Core commit, one of the report pages is now giving a result that some config item differs from its .yml file source, and that report page is therefore not a good candidate for using in the test.

I'll look into it... eventually.

CommentFileSizeAuthor
#2 2636514.patch1.35 KBjhodgdon

Comments

jhodgdon created an issue. See original summary.

jhodgdon’s picture

Title: ConfigUpdateTest needs updating » ConfigUpdateTest is failing (finding spurious differences in some config)
Status: Active » Fixed
StatusFileSize
new1.35 KB

OK. So it turns out that, for whatever reason, when you run the reports now and show differences, various config items have these new components in them:

_core
_core::default_config_hash : k3aUaZXGDuhkek2TZIee0PApOPTvYZLadziekdyHA5A

These are not in the YML files but are in the config in the database... at least if you install with the 'testing' profile and I'm not sure if it happens if you install with the Standard or Minimal. But anyway, it happens during tests.

So I think the reports and differencing classes just need to ignore these config components when showing differences, the same as we're already ignoring UUIDs.

Anyway... here's a patch. The other line in there is adding a couple of required modules (that Node requires) to the modules list in the test, which I noticed when trying to reproduce this manually by installing the Testing profile and then the additional modules, and then running the reports.

With this, the tests pass so I'm going to go ahead and commit it.

  • jhodgdon committed fdd7187 on 8.x-1.x
    Issue #2636514 by jhodgdon: ConfigUpdateTest finds spurious differences...

Status: Fixed » Closed (fixed)

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

grimreaper’s picture

Thank you very much for the patch.

I have made a patch for features to prevent exporting the _core : #2668526: Do not export _core default_config_hash