Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

ping tests are failing #1684

Closed
daviddias opened this issue Oct 31, 2018 · 2 comments
Closed

ping tests are failing #1684

daviddias opened this issue Oct 31, 2018 · 2 comments
Labels
exp/expert Having worked on the specific codebase is important P0 Critical: Tackled by core team ASAP

Comments

@daviddias
Copy link
Member

  1) HTTP API
       ## http-api spec tests
         /ping
           returns 200 and the response stream with the ping result:
     Error: Timeout of 10000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/Users/imp/code/js-ipfs/test/node.js)


  2) HTTP API
       ## http-api spec tests
         /pubsub
           /peers
             returns 200 if no topic is provided:
     Error: Timeout of 10000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/Users/imp/code/js-ipfs/test/node.js)


  3) interface-ipfs-core over ipfs-api tests
       .ping
         should fail when pinging an unknown peer:
     Error: Timeout of 60000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/Users/imp/code/js-ipfs/test/node.js)


  4) interface-ipfs-core over ipfs-api tests
       .ping
         should fail when pinging an invalid peer:
     Error: Timeout of 60000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/Users/imp/code/js-ipfs/test/node.js)


  5) interface-ipfs-core over ipfs-api tests
       .pingPullStream
         should fail when pinging an unknown peer over pull stream:
     Error: Timeout of 60000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/Users/imp/code/js-ipfs/test/node.js)


  6) interface-ipfs-core over ipfs-api tests
       .pingPullStream
         should fail when pinging an invalid peer over pull stream:
     Error: Timeout of 60000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/Users/imp/code/js-ipfs/test/node.js)


  7) interface-ipfs-core over ipfs-api tests
       .pingReadableStream
         should fail when pinging an unknown peer over readable stream:
     Error: Timeout of 60000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/Users/imp/code/js-ipfs/test/node.js)


  8) interface-ipfs-core over ipfs-api tests
       .pingReadableStream
         should fail when pinging an invalid peer over readable stream:
     Error: Timeout of 60000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/Users/imp/code/js-ipfs/test/node.js)

this is blocking the release #1635

@daviddias daviddias added exp/expert Having worked on the specific codebase is important P0 Critical: Tackled by core team ASAP status/ready Ready to be worked labels Oct 31, 2018
@daviddias
Copy link
Member Author

daviddias commented Oct 31, 2018

I've tested with the latest libp2p (version on master) and it doesn't seem to solve the problem (which means we don't have a need to accelerate the libp2p release libp2p/js-libp2p#249).

Note, the ping tests only fail when it is ipfs-api contacting the http-api, so we have indeed narrowed down the issue to the http-api / ipfs-api implementation detail.

@daviddias
Copy link
Member Author

fix is here #1685

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
exp/expert Having worked on the specific codebase is important P0 Critical: Tackled by core team ASAP
Projects
None yet
Development

No branches or pull requests

1 participant