Fix timeout in tests on Windows [1.x]#137
Conversation
Rework the test waiting for connection failure to periodically check whether the error has been reported yet, instead of having a constant timeout value.
|
The Node v0.10 failure is unrelated: I think we should start removing Node v0.10 from our CI builds, what do you think @rmg and @superkhau? |
|
@bajtos Thanks for fixing the windows issues. 👏 WIth regard to removing CI builds, yes we should removing it ASAP. We're just wasting time working on those issues now IMO. You also sent the notification on GG announcement regarding the dropping -- did you hear anything back yet? |
No, see https://groups.google.com/forum/#!topic/loopbackjs/b9MCPOHrUgk The post got only 21 views, looks like there are not many people watching the mailing list. |
|
The GG post wasn't pinned to the top (I pinned it now for you), so that would probably mean less views.
We gotta do something about that. ;) I don't blame them though because we haven't really been responding promptly there IMO. |
Rework the test waiting for connection failure to periodically check whether the error has been reported yet, instead of having a constant timeout value.
See also #135 that fixed the CI on
master.cc @superkhau