-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Unit test error with mocha and chai Timeout of 2000ms exceeded. For async tests and hooks #2868
Comments
Did you configure the transaction confirmation blocks? (https://web3js.readthedocs.io/en/1.0/web3.html#transactionconfirmationblocks) |
This comment has been minimized.
This comment has been minimized.
I tried it like this:
Was it the right way to use it? |
Please read the documentation and ask your question on stackoverflow. We also have a gitter channel with a lot of active developers. |
hi @shreyasjain did you find out what the problem was? |
I am having the same issue |
I also faced this issue and it seems like running mocha with timeout fixes this. Something like |
I had similar issue. i just change the const {interface, bytecode} to const {abi, bytecode} because we sending api in comile.JS file. const assert = require('assert'); compile.js const path = require('path'); const inboxPath = path.resolve(__dirname, "contracts", "Inbox.sol"); var output = JSON.parse(solc.compile(JSON.stringify(input))); console.log(output); module.exports.abi = outputContracts.abi; Inbox.sol // SPDX-License-Identifier: GPL-3.0 contract Inbox { |
My code:
The error while running it using npm run test:
I searched for solution in so many similar questions, but none of them helped me. Please help. I already spent hours on this issue.
Important point:
The myContract.deploy() is working fine, but myContract.deploy().send() is not. I think there is something wrong with the send() method. You can check it by downloading the gist from the link below:
Git Repository of my project: https://github.com/shreyasjain/inbox
The text was updated successfully, but these errors were encountered: