Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

client test failures #18

Open
QuChen88 opened this issue Aug 6, 2023 · 0 comments
Open

client test failures #18

QuChen88 opened this issue Aug 6, 2023 · 0 comments

Comments

@QuChen88
Copy link
Contributor

QuChen88 commented Aug 6, 2023

I noticed a few memcache-client test cases fail when I run npm test locally. I don't think this is a functional bug as the client works fine. This is most likely a test issue which would be nice to fix.

FAIL  src/test/spec/client.spec.ts (7.634 s) (10 failures)
  memcache client
    ✕ should not get system ETIMEDOUT error after custom connect timeout (2 ms)
    ✕ should set and get multiple keys concurrently with 1 maxConnections (14 ms)
    ✕ should set and get multiple keys concurrently with 2 maxConnections (11 ms)
    ✕ should set and get multiple keys concurrently with 3 maxConnections (7 ms)
    ✕ should set and get multiple keys concurrently with 4 maxConnections (7 ms)
    ✕ should set and get multiple keys concurrently with 5 maxConnections (5 ms)
    ✕ should set and get multiple keys concurrently with 10 maxConnections (3 ms)
    ✕ should handle error if can't JSON.stringify value (6 ms)
    ✕ should gracefully propagate decompress error (5002 ms)
    ✕ should handle command timeout error (105 ms)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant