Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
configuration system
Priority:
Critical
Category:
Bug report
Assigned:
Issue tags:
Reporter:
Created:
5 Dec 2014 at 08:54 UTC
Updated:
23 Dec 2014 at 10:04 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
joachim commentedComment #2
joachim commentedOops.
Test should fail.
Comment #4
almaudoh commentedThis comment doesn't match the code, the test module referred to is empty. This fails because the
config_existing_default_config_test.ymlis wrongly named, should beconfig_existing_default_config_test.info.yml. I don't know if this is intentional or not. CMI folks may want to take a look at this.Another test in the class (
::testIntegrationModuleReinstallation) also does similarModuleInstaller::install(), maybe we can extend this check to include those.Comment #5
berdir1. That is wrong, it should be renamed. Tagging Novice to do exactly that, provide a patch with that rename and the test change from the initial patch and then it should be green.
Comment #6
tadityar commentedIs this the file that should be renamed?
Comment #7
berdirI can't say, the patch doesn't contain it :)
Comment #9
rpayanmTrying...
Comment #10
berdirRename looks correct, have a look at https://www.drupal.org/documentation/git/configure for configuring git diff so that it picks up the rename as a rename and not a delete/add of a new file.
I believe we no longer add explicit hidden: true to modules in tests/modules folders, as they are automatically hidden (or non-existent, actually) when you're not within a test.
Comment #11
rpayanmConfig git successfully ! Thank you :)
Comment #12
berdirI think this is good to go, we could also check the other install() call, but I think #1719648: ModuleInstaller::install() should provide more information than simply returning FALSE when a module isn't in the file system will take care of that in a more generic and better way.
RTBC, alexpott will probably want to see this, so assigning to him.
Comment #13
joachim commentedThat's correct, #1719648: ModuleInstaller::install() should provide more information than simply returning FALSE when a module isn't in the file system will take care of crashing tests properly when a module install fails ;)
Comment #14
alexpottNice find. Committed 8e7f24f and pushed to 8.0.x. Thanks!