@loopback/rest: HttpHandler integration test times out after 2 seconds randomly

[raymondfeng]

Description / Steps to reproduce / Feature proposal

Run npm test from loopback-next.

Current Behavior

Sometimes (not always) the http handler integration test fails with timeout.

1) HttpHandler
       with a body request route
         returns 400 for malformed JSON body:
     Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/Users/rfeng/Projects/loopback4/loopback-next/packages/rest/dist8/test/integration/http-handler.integration.js)

Expected Behavior

It should pass consistently.

See Reporting Issues for more tips on writing good issues

[hacksparrow]

Tried many times, not seeing it. Anyone else want to give it a go?

[hacksparrow]

Got a timeout error but in a different location:

  1) HttpCachingProxy
       proxies HTTP requests:
     Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/Users/ibm/projects/loopback-next/packages/http-caching-proxy/dist8/test/integration/http-caching-proxy.integration.js)

[dhmlau]

Since it's marked as a bug, I'd like to tag it as DP3. Putting into our backlog.

[hacksparrow]

@bajtos did #1415 fix the intermittent this too?

[bajtos]

did #1415 fix the intermittent this too?

It's possible, but I don't really know, TBH. I haven't seen any timeouts recently though.

[bajtos]

I encountered a timeout recently, the test was not able to resolve example.com hostname into an address. This is very surprising considering that we have two tests (HTTP and HTTPS) and only one of them failed.

[bajtos]

I am proposing to increase the timeout of HttpCachingProxy tests that are talking to internet from the current default 2 second to something like 10 or even 30 seconds in order to accommodate for slow connections.

Thoughts?

[virkt25]

+1 - I’m experiencing timeouts with example-todo tests using caching in #1437

[bajtos]

Let's see if #1442 can improve the situation.