-
Notifications
You must be signed in to change notification settings - Fork 396
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsistent Runserver in Testing #4011
Comments
Note that all 3 scenarios come from the same project. I have attempted to downgrade Drush here as I did in #3968 to resolve the issue, but to no avail. I think this all comes back to one of a few things:
|
Further / expansive digging on this issue seems to indicate that at "some point" during behat testing, the drush runserver command pulls the database credentials out of the This was tested by:
When I have hardcoded credentials in the settings.php file for Lando, I get the 500 error and timeout with the `http://127.0.0.1:8888 url. When I have variables in the settings.php file and local (lando) and ci (not lando) credentials in the yml files, it seems to work fine. Note that in order to make this work, I have a PR in to "fix" #3994 (see #4013). |
Paths forward:
|
@danepowell FYI the above solution does work with Drush 9.7 but does not appear to work with Drush 10.x. For some reason I'm still getting a 500 status with Drush 10. |
@danepowell there is definitely something going on with settings here. when i removed database config from blt.yml and ci.blt.yml (so stock config) and instead did the local in example.local.blt.yml / local.blt.yml things started working again. shoutout to @lcatlett for her DDev plugin... made me think to try that here and it worked. i think we continue to get bit by something related to environment detection (and it's further exacerbated in Drush 10 FOR SOME REASON). i don't think we need to keep this issue open at this point. put your lando / ddev specific config in the local blt files and this shouldn't happen in CI. |
Hello, |
Describe the bug
I'm getting varied results with the runserver command. I believe some of this is related to #3994.
Scenario 1: Tests "Work"
In this scenario, the CI environment detection isn't actually working properly because of the Envrionment Detector issue raised in #3994. HOWEVER, if you look at the output, a few interesting things should be noted:
tests:server:start
command is not runtests:behat:run
process waits for a response fromhttp://localhost:9222
and then continues, and worksScenario 2: Tests Don't Work
The notable difference between Scenario 1 and Scenario 2 is that I "fixed" Environment Detection (so the build now "knows" it's in CI. Note that in this scenario, it does attempt to do the drush runserver (and cannot connect to it). This is related to #3968 as it's the same issue (unclear if it's the same root cause as this is a brand new BLT Project).
Note that config does not mismatch here (good, theoretically) but still doesn't seem to work.
Scenario 3: Runserver Disabled
In Scenario 3, I have manually disabled the runserver command. Note the difference in output. However, in this scenario, the tests fail (likely because the server isn't running).
The text was updated successfully, but these errors were encountered: