Skip to content
This repository was archived by the owner on Apr 3, 2019. It is now read-only.

Conversation

@vbudhram
Copy link
Contributor

@vbudhram vbudhram commented Apr 19, 2018

This PR increases timeout for recovery code related tests and fixes #338. Doing recovery code comparisons (with scrypt) was taking longer than the default 2 second timeout for tests.

    recovery codes
      ✓ should generate new recovery codes (1469ms)
      ✓ should fail to consume unknown recovery code
      ✓ should consume recovery code (3193ms)

@mozilla/fxa-devs r?

@vbudhram vbudhram added the WIP label Apr 19, 2018
@vbudhram vbudhram added this to the FxA-154: Release TOTP milestone Apr 19, 2018
@vbudhram vbudhram self-assigned this Apr 19, 2018
@ghost ghost added the waffle:active label Apr 19, 2018
Copy link
Contributor

@jrgm jrgm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

But, not sure why the change from () => { to function () {.

@vbudhram vbudhram merged commit f202197 into master Apr 19, 2018
@ghost ghost removed the waffle:review label Apr 19, 2018
@vbudhram
Copy link
Contributor Author

why the change from () => { to function () {.

Using arrow function, timeout wasn't available in the describe block. You would have to put .timeout on each test case, which seemed more clunky.

@philbooth philbooth deleted the fix-timeout branch August 19, 2018 08:11
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

circle tests flakily failing with 'Pool is closed' exception thrown

3 participants