4.1.7 test network doesn't work
See original GitHub issue- I’ve asked for help in the Truffle Gitter before filing this issue.
Issue
truffle test
says cannot connect to Ethereum client when run after truffle init
. This may be a truffle init
problem, as I don’t run into this when I truffle unbox
the MetaCoin project.
Steps to Reproduce
truffle test
Expected Behavior
normal tests to rumn
Actual Results
.nvm/versions/node/v8.9.0/lib/node_modules/truffle/build/webpack:/~/truffle-error/index.js:10
this.stack = (new Error(message)).stack;
^
Could not connect to your Ethereum client. Please check that your Ethereum client:
- is running
- is accepting RPC connections (i.e., "--rpc" option is used in geth)
- is accessible over the network
- is properly configured in your Truffle configuration file (truffle.js)
Environment
- Operating System: OSX
- Ethereum client:
- Truffle version (
truffle version
): 4.1.7 - node version (
node --version
): v8.9.0 - npm version (
npm --version
): 5.8.0
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
4.1.7 Flashcards - Quizlet
Study with Quizlet and memorize flashcards containing terms like Consider the following IPv6 address: 2001:0BEF:0BAD:0006::32/64 Drag the component parts of ...
Read more >Spring 4.1.7 + Junit 4.12 not working while executing from ...
Here the explanation for Spring 4.1.7 : The Spring TestContext Framework offers full integration with JUnit 4.9+ through a custom runner (tested on...
Read more >4.1.7. Step 7: Check Connection Table in Fitter Report - Intel
To view this report, click Processing > Compilation Report, open the Fitter > In-System Debugging folder, and click Connections to Signal ...
Read more >Solved 4.1.7) A test instrument needs to be calibrated - Chegg
Question: 4.1.7) A test instrument needs to be calibrated periodically to prevent measurement errors. After some time of use without calibration, ...
Read more >'Unknown Error' on Commit of Network and Device ...
Been hammering it all day today and trying to work out what changes cause the ... If created test user did some changes,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@Arvanaghi Any details on what was the actual cause of the message? Cause I’m having the same issue, still not finding the error.
More context: tests run perfectly well within
truffle develop
and throughsolidity-coverage
, but fail with the “could not connect” upontruffle test
. Even more baffling: the tests actually run (and pass), just at the end the error message is displayed.Apologies, I haven’t been able to reproduce the error. And I can’t recall right now what was the truffle-js file that was being used at the time (I’m working on multiple different projects). Since in my latests test runs I haven’t seen this error, I’ll regard it as “fixed” for me.
I’ll give notice in this thread in case I see the error again.