Skip to content
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

Windows: Fails to run functional tests in Firefox #52053

Open
dmlemeshko opened this issue Dec 3, 2019 · 2 comments
Open

Windows: Fails to run functional tests in Firefox #52053

dmlemeshko opened this issue Dec 3, 2019 · 2 comments

Comments

@dmlemeshko
Copy link
Member

dmlemeshko commented Dec 3, 2019

Breaking change for Windows came with the following commit: 401fa13

How to reproduce:

  1. Start Kibana server node scripts/functional_test_server
  2. Run functional tests with node scripts/functional_test_runner --config test/functional/config.firefox.js

Firefox browser is not started, the following error occurs:

debg [webdriver] Creating session
 debg [webdriver] Creating session
 warn Failure loading service "__webdriver__"
ERROR Error: remote failed to start within 2 minutes
          at Promise.race (C:\Users\LeeDr\git\kibana\test\functional\services\remote/webdriver.ts:247:13)
 warn Failure loading service "find"
ERROR Error: remote failed to start within 2 minutes
          at Promise.race (C:\Users\LeeDr\git\kibana\test\functional\services\remote/webdriver.ts:247:13)
 warn Failure loading service "browser"
ERROR Error: remote failed to start within 2 minutes
          at Promise.race (C:\Users\LeeDr\git\kibana\test\functional\services\remote/webdriver.ts:247:13)
ERROR Error: Failure initializing 3 service(s)
          at ProviderCollection.loadAll (C:\Users\LeeDr\git\kibana\packages\kbn-test\target\functional_test_runner\lib\providers\provider_collection.js:60:13)

The issue is not reproduced on MacOS and Linux

@jsanz
Copy link
Member

jsanz commented Dec 12, 2023

@dmlemeshko is this issue still valid? changing tags triggered the bot to add the needs-team, so it got in to the community duty triaging :)

@wayneseymour wayneseymour added the Team:QA Team label for QA Team label Dec 12, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/appex-qa (Team:QA)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Dec 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants