Description of the need
Currently most tests are using the Standard profile. This causes lots of unnecessary overhead on each test because most tests only need a few modules installed.
Proposed solution
Change the default profile to one that has fewer tables to copy when setting up a new test prefix.
Additional information
This will probably break tests in contrib. This should be easy to mitigate by setting protected $profile = 'standard'; if you depend on something from the standard profile, but it will require changes from module maintainers.
Recent comments
@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...
Importing the staged config throws an error: another field with the same name already exists
Thanks, I have to go out now, I will try later on and report back
Importing the staged config throws an error: another field with the same name already exists
Hi Francis. Yes, what config do you have in staging for it? You might have configs like: field.field.field_video_embed field.instance.node.page....
Importing the staged config throws an error: another field with the same name already exists