-
Notifications
You must be signed in to change notification settings - Fork 397
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
DX-5177: drush runserver problem #4609
Comments
@dpagini do you have a ci.blt.yml file in your blt directory? this runserver stuff has been problematic on other projects and i think in many cases it's because of that config. see https://github.com/Drupal4Gov/Drupal-GovCon-2017/blob/develop/blt/ci.blt.yml as a working example. i haven't had issues with runserver "not" working on the govcon repo |
This is obviously a bug in BLT. The ci.blt.yml File has nothing to do with it. This is how run server is called. But it is wrong, it does not work with the latest drush version. src/Robo/Commands/Tests/ServerCommand.php
It should be:
|
i opened a PR to test this, could you give it a shot, please? |
Tested and works on BLT 13.6.0 and Drush 11 |
Thanks all! Sorry I hadn't seen the replies back to me until now... =/ |
Describe the bug
I just updated from
13.4.0
to13.5.2
and I'm having trouble with my tests command in CI, where I'm usingdrush runserver
functionality to test my site. In my BLT update, I'm also upgrading drush from11.0.5
to11.2.1
.I can't find where I think the problem is in the diff of either of those, but I do think I see the problem.
BLT is basically calling:
$ drush runserver --uri=http://127.0.0.1:8888
but, according to the docs, there is no
--uri
option. The URI is supposed to be passed in as the primary argument, not a flag... so:$ drush runserver http://127.0.0.1:8888
To Reproduce
Given the above software versions, if I run (note the port numbers)...
Expected behavior
When I run
$ blt tss -Dtests.server.url=http://127.0.0.1:59478 -v
I want it to work.Actual behavior
It times out.
Workaround
None.
System information
The text was updated successfully, but these errors were encountered: