-
Notifications
You must be signed in to change notification settings - Fork 6.8k
build: prevent binding BrowserSync UI server during test execution #23733
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, that's a good idea. Just one suggestion on how to implement that
fd18f41
to
95272ba
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
@@ -16,12 +16,12 @@ const {root_paths: _rootPathsRaw, port, historyApiFallback} = | |||
minimist(args, {boolean: 'historyApiFallback'}); | |||
const rootPaths = _rootPathsRaw ? _rootPathsRaw.split(',') : ['/']; | |||
|
|||
const server = new DevServer(port, rootPaths, historyApiFallback); | |||
const bindUi = process.env.TEST_TARGET === undefined; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Optional when you have time: A small comment would be good here, saying that for tests like e2e the UI is not reasonable to serve, and it could cause port conflicts.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Running e2e tests locally on macOS raises various EADDRINUSE errors due to browsersync UI server trying to bind multiple times on the same port. furthermore it's not really useful having ui server running in ci tests execution