There seem to be random cases where postgres throws Drupal\Core\Installer\Exception\AlreadyInstalledException

I have mostly seen these failures in the search api and facets issue queues, because that's where I spend most of my time.

https://www.drupal.org/pift-ci-job/255377
https://www.drupal.org/pift-ci-job/255333
https://www.drupal.org/pift-ci-job/272463
https://www.drupal.org/pift-ci-job/272461
https://www.drupal.org/pift-ci-job/272441
https://www.drupal.org/pift-ci-job/273701
https://www.drupal.org/pift-ci-job/279947
https://www.drupal.org/pift-ci-job/282349

Drupal\Core\Installer\Exception\AlreadyInstalledException:
To start over, you must empty your existing database and copy default.settings.php over settings.php.
To upgrade an existing installation, proceed to the update script.

Comments

borisson_ created an issue. See original summary.

borisson_’s picture

Issue summary: View changes

We had some more random fails w/ facets

borisson_’s picture

Issue summary: View changes
borisson_’s picture

Issue summary: View changes

Another random fail w/ search api.

borisson_’s picture

Issue summary: View changes
borisson_’s picture

Issue tags: +Random test failure
drunken monkey’s picture

Could someone please take a look at this? This is making the Postgres test environment almost unusable, with it producing fails almost more often than not.

drunken monkey’s picture

Project: DrupalCI: Drupal.org Testing Infrastructure » DrupalCI: Test Runner

Maybe this is the correct queue? Sorry, I don't know, but it would really be good to get some feedback here.

andypost’s picture

That could be cause opcache and settings.php
Also http://cgit.drupalcode.org/drupal/tree/core/includes/install.core.inc#n482

Mixologic’s picture

Project: DrupalCI: Test Runner » DrupalCI: Drupal.org Testing Infrastructure
Component: Code » Unexplained Failures/Support
xjm’s picture

I think this happens on more than just Postgres; see: #2806697: Random fail for AlreadyInstalledException

Mixologic’s picture

Status: Active » Fixed

I think we've solved this issue over in https://www.drupal.org/project/drupal/issues/2906317

Status: Fixed » Closed (fixed)

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