-
Notifications
You must be signed in to change notification settings - Fork 2k
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
tests fail on gnu hurd #935
Comments
There is likely something wrong with time measurement on Hurd. |
Does the benchmark code work and terminate?
If so, does GNU Hurd trigger this macro? If that works, we can replace the standard C timing functions in the fuzzers with the ones in |
Yes, this could be attempted. |
|
Cool, then we have a way forward. Thanks! I'll update the timing code for the fuzzer tests. To test a macro triggers, I just add invalid code |
@mestia do the tests pass now that |
I confirm that tests work now. |
tests/Makefile defines
FUZZERTEST ?= -T200s
which is passed then to fuzzer tool.fuzzer -T200s
just never finishes.By running
fuzzer -v -T200s
on a hurd system I see incrementing count of test.Test runs for more than 18 hours:
i386 system:
I guess that on hurd a condition in the loop is never met for whatever reason.
Could you please also document -T flag? What -T200s does?
Thank you.
The text was updated successfully, but these errors were encountered: