Closed hudon closed 10 years ago
I think I just forgot to update "make test" Try, on one window "python src/distributiond.py" and in another "make test" On Nov 11, 2013 10:17 PM, "Robert" notifications@github.com wrote:
Looks like it gets stuck on travis.
It hangs on my machine too, I think around line 50 of
distribution.py
I'm guessing there might be some iptables rules or something I need to set up for doing the tcp stuff? Is there a way we could detect insufficient setup and tell the user to do something about it?
— Reply to this email directly or view it on GitHubhttps://github.com/Hudon/spike/pull/82#issuecomment-28264808 .
(the demon isn't running) On Nov 11, 2013 10:23 PM, "James Hudon" jameshudon@gmail.com wrote:
I think I just forgot to update "make test" Try, on one window "python src/distributiond.py" and in another "make test" On Nov 11, 2013 10:17 PM, "Robert" notifications@github.com wrote:
Looks like it gets stuck on travis.
It hangs on my machine too, I think around line 50 of
distribution.py
I'm guessing there might be some iptables rules or something I need to set up for doing the tcp stuff? Is there a way we could detect insufficient setup and tell the user to do something about it?
— Reply to this email directly or view it on GitHubhttps://github.com/Hudon/spike/pull/82#issuecomment-28264808 .
Wow, our project is actually starting to look pretty cool now. We are gonna have a nice demo. All the tests pass on my desktop btw.
Also, since we are able to run a distributed version and a non-distributed concurrent version of spike, we should have an easy way to run tests with either of these. So maybe an option for make test.
Looks like it gets stuck on travis.
It hangs on my machine too, I think around line 50 of
distribution.py
I'm guessing there might be some iptables rules or something I need to set up for doing the tcp stuff? Is there a way we could detect insufficient setup and tell the user to do something about it?