-
Notifications
You must be signed in to change notification settings - Fork 6k
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
Executable for use with AFL #1703
Conversation
Error on windows is "block mining timeout" and can thus be ignored. |
|
||
# search for test names and create ctest tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What was the reason for this block and why isn't it needed anymore?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This generated some auxiliary information so that ctest could be used as a test runner. The main advantage of ctest was that tests could be run in parallel. Since this is not possible anymore because of the IPC connection required, I did not see any reason to keep it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 for removing if not needed
cd "$REPO_ROOT" | ||
REPO_ROOT=$(pwd) # make it absolute | ||
cd "$TMPDIR" | ||
"$REPO_ROOT"/scripts/isolate_tests.py "$REPO_ROOT"/test/contracts/* "$REPO_ROOT"/test/libsolidity/*EndToEnd* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't these errors caught by soltest
? Or is the reason here to verify solfuzzer
instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These basically test solcjs
, i.e. generating all the json structures for the output, we had some bugs there before.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah right, it is a rudimentary soljson test.
@holiman please just run
solfuzz < inputfile
for fuzz-testing, this will now catch much more errors.