Installing Drupal core 8.x causes WSOD after DB credentials.

It's currently not possible to access error log data without direct access to the servers, but that's what I'm here for.

I'll try to figure something out, thanks for the report!

The only error PHP logs is the following:

Uncaught PHP Exception Drupal\Core\Database\DatabaseExceptionWrapper: "SQLSTATE[42S02]: Base table or view not found: 1146 Table 'sb6d01c7f069d370.url_alias' doesn't exist: SELECT source FROM {url_alias} WHERE alias = :alias AND langcode IN (:langcode, :langcode_undetermined) ORDER BY langcode ASC, pid DESC; Array
(
    [:alias] => favicon.ico
    [:langcode] => en
    [:langcode_undetermined] => und
)
" at /home/sb6d01c7f069d370/www/core/lib/Drupal/Core/Database/Connection.php line 569

Exception thrown when handling an exception (Drupal\Core\Database\DatabaseExceptionWrapper: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'sb6d01c7f069d370.url_alias' doesn't exist: SELECT source FROM {url_alias} WHERE alias = :alias AND langcode IN (:langcode, :langcode_undetermined) ORDER BY langcode ASC, pid DESC; Array
(
    [:alias] => favicon.ico
    [:langcode] => en
    [:langcode_undetermined] => und
)
)

But this is rather the outcome of a different issue than the issue itself.

The typical problem with MySQL on simplytest.me is that drupal core is most of the time only tested with the InnoDB driver; simplytest.me uses MyISAM as database driver and therefore crashes everytime there's a regression regarding MyISAM compatibility.

In most cases the problem is that a table could not be created because it has a primary key or index longer than 1000 bytes of data.
But there's usually a readable error for that; which might gets caught here..

I'll see if I can find out more, but that's all what the log's are giving.

issue not specific to standard profile

I was able to locally reproduce the error by adding the following to my mysql configuration file:

at [mysqld]

skip-external-locking
skip-innodb
default_storage_engine=MyISAM

Which forces the usage of MyISAM just like it is done on simplytest.me.

As far as I can see drupal core officially supports MyISAM although InnoDB is the default choice;
therefore this is a regression in drupal core

Found no current related issue in the drupal core queue, created a new one: #2270917: Limit collection name due to MyISAM restrictions and test ConfigCollectionInfo class

Closing this one.