Here are the symptoms my system is exhibiting:

1. Grab a clean checkout of HEAD.
2. Choose the default install profile.
3. Enter your (correct) DB info.
4. ERROR:
PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table '7x.variable' doesn't exist in /Applications/MAMP/htdocs/7x/includes/database/database.inc on line 1017

Which makes 0 sense, since when I look at my 7.x database it does, in fact, have a variable table in it, with 6 values:

theme_default s:7:"garland";
filter_html_1 i:1;
node_options_forum a:1:{i:0;s:6:"status";}
cron_key s:32:"bb6c45cc51af1c820dbc3666c6de84e7";
drupal_private_key s:32:"a6a3b77c06f402c7b1346a20f1efb569";
install_task s:21:"profile-install-batch";

All the rest of the tables, including vocabulary and vocabulary_node_types, which follow subsequently in the alphabet, are there as well. Curiously, watchdog is /not/ there. Hmmm....

Attached is all the info and more that you could ever hope for about this error, courtesy of xdebug.

CommentFileSizeAuthor
variable-missing-error.html35.85 KBwebchick
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

asimmonds’s picture

asimmonds CreditAttribution: asimmonds commented

I get this problem, if I have in my xdebug config:

xdebug.show_exception_trace=1

It appears install_verify_drupal() relies on the db_query() exception being silently handled, and xdebug is interfering with this.

Damien Tournoud’s picture

Damien Tournoud CreditAttribution: Damien Tournoud commented

I can reproduce if I activate xdebug.show_exception_trace.

xdebug.show_exception_trace
Type: integer, Default value: 0
When this setting is set to 1, Xdebug will show a stack trace whenever an exception is raised - even if this exception is actually caught.

Edit: incoherent rambling below.

chx’s picture

chx CreditAttribution: chx commented

even if this exception is actually caught. -- then what's the bug here??

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
CreditAttribution: webchick commented
Status: Active » Closed (won't fix)

Yep, that seems to be exactly what caused it. I don't see any way we can work around this, so marking won't fix.

Thanks, folks!

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Murphysboro, IL, USA
CreditAttribution: mikeryan commented

Just want to capture this in case anyone else runs into it - I hit the same symptom, and disabling xdebug did nothing to help me. Disabling eaccelerator was what ultimately did the trick for me, although it looks like only disabling the optimizer should do it (or upgrading eaccelerator):

http://eaccelerator.net/ticket/242

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Murphysboro, IL, USA
CreditAttribution: mikeryan commented

Tried just disabling the optimizer, no luck - I'm sticking with disabling the whole extension.