Updated: Comment #0

Problem/Motivation

Since November 18 or 19, numerous unrelated tests have been failing randomly on the testbots with the following error:

Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 268435456 bytes) in /var/lib/drupaltestbot/sites/default/files/checkout/core/lib/Drupal/Core/Database/Connection.php on line 336

It is not may always be in Connection.php.

Examples:
https://qa.drupal.org/pifr/test/674688
https://qa.drupal.org/pifr/test/674683

The fatal occurs in completely random tests, sometimes just one fail, sometimes hundreds.

Proposed resolution

Track down and revert the cause of this regression, and then profile to determine how to fix that patch.

Remaining tasks

TBD

API changes

TBD

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

xjm’s picture

Issue summary: View changes
rfay’s picture

We can easily increase the testbot memory_limit, which hopefully could give some breathing space to chase this. Unless it has to do with recursion or something that has nothing to do with actual memory space.

We can make available a dedicated testbot for doing some git bisect action to try to sort this out.

xjm’s picture

Issue summary: View changes
xjm’s picture

@amateescu reverting a suspect commit:
https://drupal.org/comment/8200987#comment-8200987

rfay’s picture

@amateescu pointed out https://qa.drupal.org/pifr/test/675143 so I grepped on that server and found no sign of the error message (grep -r in /var/log after failing in /var/log/apache2). Then I realized this message must come from run_tests.sh instead of Apache/php

xjm’s picture

amateescu’s picture

xjm’s picture

This is probably the one (from @amateescu). You can see the results of testing it in https://drupal.org/comment/8202607#comment-8202607. The one fail appears to be legitimately a bot issue and not related to the regression, see: https://qa.drupal.org/pifr/test/675568

catch’s picture

Status: Needs review » Fixed

Rolled that back. Thanks for the bisecting!

Status: Fixed » Closed (fixed)

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