-
Notifications
You must be signed in to change notification settings - Fork 277
Test installation on some larger projects #10
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
Comments
In principle, tool will run on melonport. Report looks like this. Truffle / Solidity-Parser are having a problem with some stub contracts they have, but otherwise everything works. Chronobank - which had tests failing under coverage because there was no events filtering also works. They're pushing lots of code to a development branch right now though . . . |
Numerai report looks like this They had a couple issues worth pursuing. This line in their contracts throws a solidity-parser error while instrumenting (but not when compiling with Truffle). Putting the return statement on the same line as the function call resolved it but this may be an SP regression bug. The fork we use is several commits ahead of the published version Truffle uses. And some of their minting tests fail non-deterministically under coverage - these fire events. This appears to be a timing related bug (so, basically bad news). |
Bancor @ commit 6e0f2d2 : Lots of tests but not running clear ATM . . . . holding off on this. |
Aragon has a lot of hardcoded gas values - I tried replacing those with much higher sends, and also tried funding accounts with tons of gas. But it still exits with out of gas when deploying the contracts. Just don't know what to do . . . . Possibly revisit. FWIW everything seems to instrument and compile correctly. UPDATE |
0xProject solved by @maurelian. |
Changes made for 0x:
|
Closing - no longer really doing this kind of validation. |
(events have to be resolved)(?) (requires Add option to include other folders in the coverage envelope #39)(Cannot figure this out . . . see below).And possibly PR these in? If useful?
The text was updated successfully, but these errors were encountered: