-
-
Notifications
You must be signed in to change notification settings - Fork 366
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
Fix Travis #168
Comments
The three most recent Travis builds all failed in exactly the same way, always a TimeoutError and always on Node 10 but not Node 12. Seems kinda fishy, no? Also, it says the timeout is 30 seconds which seems pretty reasonable to me. |
Could be, but from experience, it's almost always Travis being slow, especially when the problem is only on older Node.js versions. Could also be a race issue in the code or test. |
It's not definitely a race issue. I've experienced it also when developing |
@issuehunt has funded $40.00 to this issue.
|
I will give this a try |
@sindresorhus has rewarded $36.00 to @dirathea. See it on IssueHunt
|
https://travis-ci.com/sindresorhus/ky/jobs/227726270
Travis is slow. I think we might just need to increase the Puppeteer timeout somehow.
IssueHunt Summary
dirathea has been rewarded.
Backers (Total: $40.00)
Submitted pull Requests
Tips
IssueHunt has been backed by the following sponsors. Become a sponsor
The text was updated successfully, but these errors were encountered: