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

Question: wct-mocha: Is there a way to configure ChildRunner.loadTimeout? #3457

Open
mdgbayly opened this issue Sep 17, 2019 · 1 comment
Open
Labels

Comments

@mdgbayly
Copy link

mdgbayly commented Sep 17, 2019

We run wct tests using Travis/Sauce, and since upgrading to wct-mocha we found that tests periodically timeout with an error like:

Timed out loading http://localhost:8081/components/d2l-activities/test/d2l-activity-list-item/d2l-activity-list-item-test.html
    <unknown> at   <unknown> at /node_modules/wct-mocha/wct-mocha.js:841:0

I've tracked this down to this line in ChildRunner

static loadTimeout = 60000;

Through using Sauce's extended debugging, I was able to see that sometimes it does seem like the sheer number of es modules being loaded dynamically by the test, through presumably the Sauce connect tunnel, does cause the loading of the test to take longer than 60 seconds. I'm not sure of a way to improve that, so ideally I'd just like to bump the ChildRunner.loadTimeout from 60s to say 120s.

@mdgbayly mdgbayly changed the title Question: Is there a way to configure ChildRunner.loadTimeout? Question: wct-mocha: Is there a way to configure ChildRunner.loadTimeout? Sep 17, 2019
@stale
Copy link

stale bot commented Sep 17, 2020

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.

@stale stale bot added the wontfix label Sep 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant