Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Drupal 8.1.0, with RefreshLess enabled:
PHPUnit 4.8.11 by Sebastian Bergmann and contributors.
E
Time: 1.32 minutes, Memory: 4.00Mb
There was 1 error:
1) Drupal\Tests\toolbar\FunctionalJavascript\ToolbarIntegrationTest::testToolbarToggling
Zumba\GastonJS\Exception\JavascriptError: One or more errors were raised in the Javascript code on the page.
If you don't care about these errors, you can ignore them by
setting js_errors: false in your Poltergeist configuration (see documentation for details).
AjaxError:
An AJAX HTTP error occurred.
HTTP Result Code: 500
Debugging information follows.
Path: /toolbar/subtrees/h44VigUWX0CKpfG-F2mSPWyAQ6j34qKtKGcs2os92wg
StatusText: Internal Server Error
ResponseText: {"message":"A fatal error occurred: SQLSTATE[42S02]: Base table or view not found: 1146 Table \u0027drupal.simpletest977695key_value\u0027 doesn\u0027t exist: SELECT 1 AS expression\nFROM \n{key_value} key_value\nWHERE ( (name = :db_condition_placeholder_0) AND (collection = :db_condition_placeholder_1) ); Array\n(\n [:db_condition_placeholder_0] =\u003E system.theme.files\n [:db_condition_placeholder_1] =\u003E state\n)\n"}
AjaxError:
An AJAX HTTP error occurred.
HTTP Result Code: 500
Debugging information follows.
Path: /toolbar/subtrees/h44VigUWX0CKpfG-F2mSPWyAQ6j34qKtKGcs2os92wg
StatusText: Internal Server Error
ResponseText: {"message":"A fatal error occurred: SQLSTATE[42S02]: Base table or view not found: 1146 Table \u0027drupal.simpletest977695key_value\u0027 doesn\u0027t exist: SELECT 1 AS expression\nFROM \n{key_value} key_value\nWHERE ( (name = :db_condition_placeholder_0) AND (collection = :db_condition_placeholder_1) ); Array\n(\n [:db_condition_placeholder_0] =\u003E system.theme.files\n [:db_condition_placeholder_1] =\u003E state\n)\n"}
at http://localhost/core/misc/ajax.js?v=8.1.1:965 in error
at http://localhost/core/misc/ajax.js?v=8.1.1:510 in complete
at http://localhost/core/assets/vendor/jquery/jquery.min.js?v=2.1.4:2 in j
at http://localhost/core/assets/vendor/jquery/jquery.min.js?v=2.1.4:2 in fireWith
at http://localhost/core/assets/vendor/jquery/jquery.min.js?v=2.1.4:4 in x
at http://localhost/core/assets/vendor/jquery/jquery.min.js?v=2.1.4:4
/var/www/html/vendor/jcalderonzumba/gastonjs/src/Browser/BrowserBase.php:119
/var/www/html/vendor/jcalderonzumba/gastonjs/src/Browser/BrowserBase.php:99
/var/www/html/vendor/jcalderonzumba/gastonjs/src/Browser/BrowserCookieTrait.php:54
/var/www/html/vendor/jcalderonzumba/mink-phantomjs-driver/src/SessionTrait.php:45
/var/www/html/vendor/jcalderonzumba/mink-phantomjs-driver/src/SessionTrait.php:37
/var/www/html/vendor/behat/mink/src/Session.php:78
/var/www/html/vendor/behat/mink/src/Mink.php:186
/var/www/html/core/tests/Drupal/Tests/BrowserTestBase.php:506
FAILURES!
Tests: 1, Assertions: 10, Errors: 1.
With RefreshLess disabled:
PHPUnit 4.8.11 by Sebastian Bergmann and contributors.
.
Time: 1.52 minutes, Memory: 4.00Mb
OK (1 test, 10 assertions)
My Questions
1. Is it true that SIMPLETEST_BASE_URL
is supposed to be set to the URL that I can access my site with (i.e. the default profile) and then Simpletest module will know to serve the testing environment instead of the default environment?
2. What I don't understand is that since the test runs in a separate environment, why would enabling a module on the "default" profile affect tests?
Thanks!
Comment | File | Size | Author |
---|---|---|---|
#29 | 2724813-29.patch | 1.05 KB | alexpott |
#29 | 27-29-interdiff.txt | 1.03 KB | alexpott |
#27 | 2724813-27.patch | 840 bytes | alexpott |
#26 | 2724813-26.patch | 2.2 KB | alexpott |
#25 | postgres5.patch | 4.15 KB | alexpott |
Comments
Comment #2
ztl8702 CreditAttribution: ztl8702 as a volunteer commentedComment #3
ztl8702 CreditAttribution: ztl8702 as a volunteer commentedComment #4
ztl8702 CreditAttribution: ztl8702 as a volunteer commentedComment #5
chx CreditAttribution: chx at Smartsheet commentedhttps://www.drupal.org/pift-ci-job/331959
https://www.drupal.org/pift-ci-job/331953
etc.
Comment #6
alexpottI don't think refreshless has to be enabled for this to happen. Is it a reliable fail with the refreshless module in the code base? Also this has been occurring for ages and I just can't see how this is critical. Annoying yes, but it's happening on a new and still experimental testing infrastructure and it's postgres. It's good to have an issue for this though.
Comment #7
tedbowI get this error without refreshless in my code base.
Comment #8
tedbowSorry I was wrong. I am not getting same error.
Comment #9
dawehnerYeah I don't think its related with refreshless to be honest, but rather somehow an issue with the testbot. I tried to run the test quite often locally and it continued to work without a random test failure :(
Comment #10
jibranComment #11
jibranIt doesn't only fail on testbot. I tried it on travis as well.
https://travis-ci.org/jibran/drupal/jobs/139011739
https://travis-ci.org/jibran/drupal/jobs/139011743
https://travis-ci.org/jibran/drupal/jobs/139011751
Comment #12
jibranWell, it is not random at all. It failed on all php versions for all DB drivers. I don't know why testbot is not failing it.
PHP 5.5
PHP 5.6
PHP 7
Comment #13
dawehner@jibran
Did you checked which version of phantomjs is used on travsci? We updated to phantomjs 2 explicitly to fix failures which looked kinda similar.
Comment #14
jibranYes you are right @dawehner it was a version issue not it is passing fine https://travis-ci.org/jibran/drupal/builds/139106721
Comment #15
dawehnerHa, life would have been too easy :)
Comment #16
alexpottComment #18
alexpottComment #19
alexpottComment #20
alexpottComment #21
alexpottComment #23
alexpottComment #24
alexpottComment #25
alexpottComment #26
alexpottComment #27
alexpottDiscussed more with @dawehner and we felt that any JavascriptTestBase test could hit this - we need to wait for any AJAX activity to finished before tearing down.
Comment #29
alexpottImproving the tear down so even if the waiting fails we don't get messages about the session table but something useful that points out what is happening.
Comment #30
dawehnerI agree of not using the assertion, its a tear down functionality here.
Comment #31
catchThe comment is a bit confusing, here's a suggestion:
Comment #32
alexpott@catch that looks perfectly clear.
Comment #33
catchFixed that comment on commit.
Committed/pushed to 8.2.x and cherry-picked to 8.1.x. Thanks!