-
Notifications
You must be signed in to change notification settings - Fork 299
fix: increase timeout for name.publish and fix setup code #749
Conversation
Could we instead of raising the timeout, make sure the daemon is started in offline mode for this test? In offline mode, the publish operation takes about 0.01 seconds, and gives the same output as-if it was online. |
I'm guessing the |
It would, as long as we're using the same daemon. |
hmm, interesting bug,
I've added an issue here: ipfs/kubo#4978 I'm happy to change to using offline mode but it's not possible right now...we need the node ID so the tests can assert on the publish result. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @alanshaw.
I'm really not a fan of having us use live IPNS in tests when it's as slow as it is. Can we investigate and see if providing the |
Note it is not "live" as in "live network", the tests spin a mini IPFS network of 3 nodes. |
name.publish
takes forever! I've increased the timeout to 5 minutes to accommodate.I also moved the test (which adds a file for future tests) into the
before
block, I've removed the assertions that this test was making (there should be adequate tests for adding files elsewhere) and instead of hard coding the CID I've extracted it from the return value of thefiles.add
call.