Updated Drupal to 8.6. This goes with the following updates because it's possible...

[yaffs-website] / web / core / modules / system / tests / src / Functional / Entity / Update / MoveRevisionMetadataFieldsUpdateTest.php

diff --git a/web/core/modules/system/tests/src/Functional/Entity/Update/MoveRevisionMetadataFieldsUpdateTest.php b/web/core/modules/system/tests/src/Functional/Entity/Update/MoveRevisionMetadataFieldsUpdateTest.php
index b4888db0985ade5c44f3c6353c3a5da4a0ebd65f..62d9a3e3fe57f493e9737dea06cbc72a130ed314 100644 (file)
--- a/web/core/modules/system/tests/src/Functional/Entity/Update/MoveRevisionMetadataFieldsUpdateTest.php
+++ b/web/core/modules/system/tests/src/Functional/Entity/Update/MoveRevisionMetadataFieldsUpdateTest.php
@@ -10,6 +10,7 @@ use Drupal\views\Entity\View;
  * Tests the upgrade path for moving the revision metadata fields.
  *
  * @group Update
+ * @group legacy
  */
 class MoveRevisionMetadataFieldsUpdateTest extends UpdatePathTestBase {
 
@@ -141,7 +142,7 @@ class MoveRevisionMetadataFieldsUpdateTest extends UpdatePathTestBase {
     $revision_metadata_keys = [
       'revision_user' => 'revision_user',
       'revision_created' => 'revision_created',
-      'revision_log_message' => 'revision_log_message'
+      'revision_log_message' => 'revision_log_message',
     ];
     $this->assertEquals($revision_metadata_keys, $entity_type->getRevisionMetadataKeys(TRUE));
 
@@ -167,7 +168,7 @@ class MoveRevisionMetadataFieldsUpdateTest extends UpdatePathTestBase {
     $definition = [
       'id' => 'entity_test_mul_revlog',
       'revision_metadata_keys' => [
-        'revision_default' => 'revision_default'
+        'revision_default' => 'revision_default',
       ],
     ];
     $entity_type = new ContentEntityType($definition);