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
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.
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.
We run wct tests using Travis/Sauce, and since upgrading to wct-mocha we found that tests periodically timeout with an error like:
I've tracked this down to this line in ChildRunner
https://github.com/Polymer/tools/blob/fbc1a8f77aef7fa62bbb06c90282624a794464a4/packages/wct-mocha/src/childrunner.ts#L81
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.