Testrpc does not exit upon coverage competion (Linux)
See original GitHub issueIf I run coverage twice, testrpc will throw Error: listen EADDRINUSE :::8555
on the second try.
As a result I have to manually close the testrpc process spawned by solidity-coverage before running again. It looks as though it should kill the process from a brief look through the code.
OS is Ubuntu 16.04.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:15 (6 by maintainers)
Top Results From Across the Web
testrpc doesn't run directly · Issue #380 - GitHub
When entering testrpc at the home/user directory, the output is testrpc: command not found . Possible Solution. Entering /opt/node/lib/ ...
Read more >command Testrpc is not working - Ethereum Stack Exchange
testrpc is not recognized as an internal or external command,operable program or batch file. Is there any additional package or something that I ......
Read more >Install testrpc on Linux | Edureka Community
Hi. I am new to ethereum and I am trying to create an ethereum private network for which I need testrpc to run....
Read more >A List Of Error Messages When Running Testing tools in Solidity
A list of error messages when running testing tools, and the methods of how to deal with them. Update irregular. Contributions are welcome....
Read more >The TestRPC | Ethereum Nodes - InformIT
Learn how to run and interact with an Ethereum node.
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 FreeTop 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
Top GitHub Comments
Should be fixed in
0.5.1
. Thanks again @fvictorio.Please ping if this is not the case. Tested strategy by launching testrpc-sc twice in succession in a Travis Ubuntu container here.
Can confirm, this is happening to me too in Ubuntu 17.10.