-
Notifications
You must be signed in to change notification settings - Fork 54
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
Fuzzer engine, spurious failures #102
Comments
Is this the codeline that stores the trace? https://github.com/ethereum/evmlab/blame/master/utilities/fuzzer.py#L143 |
It reappeared again, but I have some more log output this time:
So, apparently, this is what happens when we try to do the
|
Related: moby/moby#31230 |
Actually, now that we know what it is. we don't really have to fix it. If there is any output from the process, we know the instantiation failed (otherwise the output would have wound up into the file, since we pipe everything to file). And then we can just rerun the testcase, and move on. |
Same, on the second machine with more up-to-date code:
|
Sometimes, this happens:
I ran the testcase in question manually inside the parity docker image, and it worked fine. But for some reason, the file didn't exist. Disk was not full. It happened after
573182
testcases, so it doesn't happen often.The text was updated successfully, but these errors were encountered: