Closed fabcotech closed 5 years ago
When you run $ node test/liveRNodeTest.js rnode-test.rhobot.net 50000
it looks like trying the test against the node at rnode-test.rhobot.net on port 50000. In that case it wouldn't matter what version of rnode you're running, but what version is running on that server.
But for some reason it seems it is trying to deploy against your local node anyway based on endpoint: { host: 'localhost', port: 40401
I didn't remember that we supported testing against remote nodes, although it seems like a good idea.
Looks like this is how the endpoint is calculated https://github.com/rchain-community/rchain-api/blob/master/test/liveRNodeTest.js#L139-L142
Not sure how to set those environment variables.
@dckc I guess you might be able to help with the environment variables?
In any case @fabcotech, can you confirm that the test passes when run against your local node?
I modified the endpoint
variable so it points to my local rnode process:
const endpoint = {
host: "localhost",
port: parseInt("40401", 10)
};
The test fails with the same error. Do the tests pass on your machine ?
wishing for ci with a live node...
Confirming @fabcotech 's experience on Debian 9.5, RNode 0.8.2, rchain-api a45d49fc360787e73724450b8771e1ec352c4ca2
RNode output was
17:52:17.126 [node-runner-16] INFO c.r.casper.MultiParentCasperImpl - Received Deploy #1548543136942 -- new x0, x1 in {
@{"publ...
npm run integrationTest
is working for me now that #62 is done, and it includes listenForDataAtName
, I'm pretty sure.
Let us know if not.
Hi !
I'm running the last version of
rnode
(0.8.3), and a fresh install ofrchain-api
.When running
node test/liveRNodeTest.js rnode-test.rhobot.net 50000
Which is a test tu post data on-chain and then read it through a GRPC call. I've got an error and the test fails:It seems that the
listenForDataAtName
call does not work :(