Skip to content

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

Open
@mdgbayly

Description

@mdgbayly

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions