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

intermittent issue related to Fetch Error network timeout #515

Closed
shahidv3 opened this issue Jan 27, 2019 · 3 comments
Closed

intermittent issue related to Fetch Error network timeout #515

shahidv3 opened this issue Jan 27, 2019 · 3 comments

Comments

@shahidv3
Copy link

shahidv3 commented Jan 27, 2019

Hello All,
I have recently migrated to 2.x and noticed that the test runs are inconsistent with the following stack trace.Did anyone faced this . I tried increasing the timeout and .catch handling as mentioned in the following links
#393
#483

However it didn't helped. Appreciate the response @H1Gdev @vlucas

**FetchError: network timeout at: https://<api_url>/someroute

  at node_modules/node-fetch/lib/index.js:1437:13
  at Timeout.callback (node_modules/jsdom/lib/jsdom/browser/Window.js:678:19)**

Thanks , Sahid

@H1Gdev
Copy link
Collaborator

H1Gdev commented Jan 28, 2019

@shahidv3

From stack trace, It seems that frisby timeout is not enough.(default is 5000[ms])

First, please try increasing each timeouts like following sample code.

const frisby = require('frisby');

let timeout = 10000; // wait 10000[ms].

it('issue 515.', () => {
  return frisby.timeout(timeout)
    .get('https://<api_url>/someroute');
}, timeout);

@shahidv3
Copy link
Author

thanks @H1Gdev , its working fine now.
appreciate your quick response.

@vlucas
Copy link
Owner

vlucas commented Jan 30, 2019

Thanks @H1Gdev !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants