-
Notifications
You must be signed in to change notification settings - Fork 201
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
Slow on Windows #976
Comments
To make it clear, the program is waiting on this asynchronous call: which in turn is waiting on this array of promises: The which on windows are defined here: |
See the launchpad issue for an alternative fix proposal of using the known browsers from the configuration file if they exist, otherwise falling back to the slow |
Another option to speed-up the browser detection is to use launchpad's env variables: |
Unfortunately the launchpad environmental variables didn't help for me, has it helped others on this thread? |
The following environment variable values have saved me in Win10 environment:
It is not obvious from Polymer and launchpad documentation the need to set only single browser with known location to minimize the test run time during ongoing development. Of course for multiple browsers it will take more time and traverse over all PATH with guess on all possible browsers takes forever. It would be reasonable not to rely on auto-detection and list in LAUNCHPAD_BROWSERS only browsers you have set the LAUNCHPAD_xxx location. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed after being marked stale. If you're still facing this problem with the above solution, please comment and we'll reopen! |
There was an issue about slow execution of tests on Windows:
https://github.com/Polymer/web-component-tester/issues/169
However, the issue persists. Perhaps it's slightly faster now, though.
The reason appears to be that even though launchpad immediately finds the browser required for running tests (in my case Chrome), it takes a long time to find all the available browsers.
You can see the logs below (I've added some extra logging too):
The slow step here is from 17:06:03 to 17:07:12, e.g. more than a minute
My proposed fix is for the
api.browsers
function in launchpad to take in an optional argument specifying which browsers to find, and for wct-local to supply these based on the configuration.The text was updated successfully, but these errors were encountered: