-
Notifications
You must be signed in to change notification settings - Fork 2.3k
With a large enough contracts set to compile truffle hangs running tests. #1659
Comments
Note: if you switch to solc 0.5.3 the above doesn't hang but instead does try to spit out an error message, but the code in truffle-compile module is trying to dereference "e" instead of "err". Her's the output using solc 0.5.3:
|
If you can explain how to build/run truffle locally on windows I can perhaps help fix things like this and give you PR's rather than bug descriptions. |
Do the instructions in the README work for you on Windows? Let me know if they don't and we can get that sorted out. Thanks a bunch! |
I have the same issue on macOs 10.14.2 |
How about Solidity 0.5.6 and Truffle v5.0.8? Does this change anything? Does the same |
Same problem with 0.5.6 and 5.0.8. If you add the large number of contracts test to your release testing suite, you should hit it. |
Still seeing the same on 5.0.9 workaround for us by deleting the |
I got the same issue with 5.0.13 Truffle v5.0.13 (core: 5.0.13) |
Seems to be OK with the below setup (on Windows): Truffle v5.0.20 (core: 5.0.20) But I think this is because it is recompiling every time regardless, see #469 (comment) |
Looks like this is solved!! 🥇 If there is still some problem here, feel free to open another issue! Thanks |
Issue
With a large enough contracts set to compile, the profiling check (I believe) to see if re-compilation needs to occur when running a test suite hangs indefinitely on windows 10.
I would guess it is a race condition/thread starvation problem and the profiling threads need to be sent out in chunks with a max threads per chunk value.
Steps to Reproduce
Using truffle 5.0.2 and solc 0.5.2 on windows 10 x64:
Expected Behavior
Truffle recognizes no compilation needs to occur and starts the test suite.
Actual Results
Hangs indefinitely with this output:
Environment
truffle version
): Truffle v5.0.2 (core: 5.0.2)node --version
): Node v10.15.0npm --version
): 6.4.1The text was updated successfully, but these errors were encountered: