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

kademlia-1.1.0.0 test suite runs too long #2

Open
peti opened this issue Sep 2, 2015 · 6 comments
Open

kademlia-1.1.0.0 test suite runs too long #2

peti opened this issue Sep 2, 2015 · 6 comments

Comments

@peti
Copy link

peti commented Sep 2, 2015

Hi, we packaged kademlia on NixOS, but unfortunately our central builds fail with a timeout error during the test suite run. Is it normal for that test suite to run for 2+ hours? Please see http://hydra.nixos.org/build/25334361/log/raw for a complete build log.

@froozen
Copy link
Owner

froozen commented Sep 2, 2015

The tests take 55 seconds on my laptop, so I can't realy imagine it taking 2+ hours, even on a busy hydra.
This probably means that something goes wrong during those tests, but I can't think of anything that could cause the tests not to finish.
There is a lot of stuff being sent between sockets during the tests, could that be a problem on a hydra?

@peti
Copy link
Author

peti commented Sep 2, 2015

Does the test suite depend on a nameserver or an public Internet access? Because those options are unavailable to Hydra builds.

@froozen
Copy link
Owner

froozen commented Sep 2, 2015

Nope, all the communication is between UDP sockets on localhost in the portrange of 1123-1142.
A failure to connect should result in a failure of the test, though, so that shouldn't be a problem.

@peti
Copy link
Author

peti commented Sep 2, 2015

Well, in that case I'm not sure how to explain this phenomenon. The test ran on i686. Maybe that makes a difference?

@photm5
Copy link

photm5 commented Sep 2, 2015

I’m currently running the tests on my ThinkPad X40 (Which is i686). I started them about 20 minutes ago, and they are still running.

EDIT: I killed it after about 2 hours and 50 minutes as it started to eat my memory. (It was at 1G swap already)

taktoa referenced this issue in dfinity-lab/kademlia Sep 7, 2018
add configuration for number of lookup nodes in parallel
@idcm
Copy link

idcm commented Aug 20, 2020

The same happens for windows 10 (which is x86-64).

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

4 participants