Broken unit tests #18
Comments
|
this is unfortunately the way the tests are designed for now. |
tylerlevine
pushed a commit
that referenced
this issue
Oct 1, 2019
Add `supports-tokens` feature to eth and teth
dhoffmann
pushed a commit
that referenced
this issue
Apr 27, 2021
* If fastcurve returns a falsey value (for example, if it determines that a signature is invalid and returns false from verify), it will be treated as though the fast path is not available, and will attempt to re-verify using the slow path. Signed-off-by: Tyler Levine <tyler@bitgo.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The unit tests seems to be broken due to the hardcoded
tester@bitgo.comtest user being inexistant on the test platform. Please confirm that the test password for this account issuperhardseypassphraseand make it obvious in the documentation or README once restored. If I'm wrong, please add more instructions to the README.I tried with my personal account on the test platform and it went fine for a while, until it reaches the tests with the hardcoded wallets and such.
The text was updated successfully, but these errors were encountered: