Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

AWS Lambda Mock Context Failing Tests

See original GitHub issue

It seems like this is causing some errors occasionally that cause tests to fail.

Error: Task timed out after 3.00 seconds
  null._onTimeout (node_modules/aws-lambda-mock-context/index.js:68:17)

Issue Analytics

State:
Created 6 years ago
Comments:6 (5 by maintainers)

Top GitHub Comments

1reaction

southpolestevecommented, Jun 7, 2017

Is this all due to the lib we are using? If so we should just bail on it and make our own. We should throw and error on using those old methods.

On Jun 7, 2017 10:29 AM, “Chris Olszewski” notifications@github.com wrote:

I think issues are being caused since we don’t cxt.succeed() the timeout triggers so even when a function run is successful if the process is still running 3 seconds later, context will throw a timeout error.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/bustle/shep/issues/240#issuecomment-306812269, or mute the thread https://github.com/notifications/unsubscribe-auth/AAcxaGyxvAR0m4t1lphl2PyB0POrq5jfks5sBrOxgaJpZM4NrwSw .

0reactions

chris-olszewskicommented, Jun 7, 2017

I think issues are being caused since we don’t cxt.succeed() the timeout triggers so even when a function run is successful if the process is still running 3 seconds later, context will throw a timeout error.